-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New PR and Branch for test #8720
Conversation
|
1 similar comment
|
|
Terraform Plan Summary
|
|
|
|
1 similar comment
|
Terraform Plan Summary
|
|
|
|
Terraform Plan Summary
|
|
Terraform Plan Summary
|
|
Terraform Plan Summarycore-vpc-production |
Terraform Plan Summarycore-vpc-development |
Terraform Plan Summarycore-vpc-test |
Terraform Plan Summarycore-vpc-preproduction |
Terraform Plan Summarypagerduty |
|
Terraform Plan Summarycore-security-production |
Terraform Plan Summarycore-logging-production |
Terraform Plan Summarycore-shared-services-production |
Terraform Plan Summarycore-network-services-production |
Terraform Plan Summarygithub |
Terraform Plan Summarysingle-sign-on |
Terraform Plan Summarymodernisation-platform-account |
Terraform Plan Summarycore-vpc-development |
Terraform Plan Summarycore-vpc-production |
Terraform Plan Summarycore-vpc-preproduction |
Terraform Plan Summarycore-vpc-test |
Terraform Plan Summarypagerduty |
|
Terraform Plan Summarycore-security-production |
Terraform Plan Summarycore-network-services-production |
Terraform Plan Summarycore-logging-production |
Terraform Plan Summarycore-shared-services-production |
Terraform Plan Summarygithub |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
A reference to the issue / Description of it
As part of issue #8669 we wanted to add a terraform summary as a comment to a Pr that ran any terraform plan so that it could show the number of changes if this was different than expected then the engineer could look at the plan to see what the extra changes where
How does this PR fix the problem?
changes the way the plan script works add in a new section to output the comment also add logic so you can ether define the name of the work flow from an input or from the workspace id. also added more robustness to the redacting script
How has this been tested?
Please describe the tests that you ran and provide instructions to reproduce.
tested on github actions and the results are bellow
Deployment Plan / Instructions
Will this deployment impact the platform and / or services on it?
{Please write here}
Checklist (check
x
in[ ]
of list items)Additional comments (if any)
{Please write here}