Comment on what happened in the plan

[EdersonSC]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always To analyze at the time of the pull request what was being planned in the plan I would go to the pipeline task. to be able to approve

Describe the solution you'd like
Something easier to analyze and approve the pull request

Describe alternatives you've considered
I would like a comment on Azure Devops, at the time of the pull request

Additional context
I have already created it for my use, and I would like you to check if it can be part of the package.

The comments.yaml file is inside the templates directory, and after the plan we call comments.yaml and it will only be triggered if it is a pull request, as it will comment on the result of the Plan.

Please change the extension from Json to Yaml

comments.json

[anwather]

I do like this - it would be good to have it included in the starter kit templates. Can you work to make this part of that?

[jeremiahhoward]

This is LOVELY @EdersonSC
We actually just created a new extended reporting feature in the hydration kit , and this is a good amount of the json conversion work that I was anticipating. I'll get this into the next release, I think. It shouldn't be a big lift.

[jeremiahhoward]

@EdersonSC Also, you may want to check out the Build-HydrationDeploymentPlans -ExtendedReporting Feature. If you do, please let us know what you think?

[EdersonSC]

Great! I'll test it and let you know...go ahead!

[jeremiahhoward]

I should have an integrated version of this out in the next week or so.

[jeremiahhoward]

@EdersonSC this should be in the next release.

[apybar]

@jeremiahhoward - is this good to close?

[cjtous1]

@jeremiahhoward :I like the amount of details provided with the extended reporting. That being said, I would really like to have something similar to what @EdersonSC built that I could run as part of my pipeline to provide a concise summary what is going to be done in the environment with a way to drill down into the details (similar to what is provided in the extended reporting) in order to understand why the change is happening if the plan is not exactly what I expected.

[apybar]

@EdersonSC - if you're still working on this I'm going to testing this after I finish the Lighthouse updates. I would love to have something like this be part of an upcoming release.

[cjtous1]

@apybar : Can we get someone else to work on this feature if @EdersonSC is not responding?
Thanks.

[apybar]

@cjtous1 - yes. I'll take a swing at it 🙂

[anwather]

@apybar - check out this branch, it was what I was getting Copilot to write - might be a good base.

#1131