[#184537961] Get personal static ips from paas-trusted-people #591
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Changes for pivotal tracker storey. Made related changes to paas-cf, paas-trusted-people and paas-aws-account-wide-terraform repos.
How to review
The new procedure for testing changes to paas-bootstrap is to run the branch into a new bootstrap environment.
Ensure that the PAAS_TRUSTED_PEOPLE_BRANCH var is set to the related branch in the paas-trusted-people repo before uploading the secrets.
Once the terraform jobs have completed check that you have the same access to the system components as you had before.
The expunge-concourse concourse job should not remove the user_static_cidrs from the security groups.
Who can review
The change should be tested by anyone with a current static ip address exposed in paas-cf and paas-bootstrap.
🚨⚠️ Please do not merge this pull request via the GitHub UI ⚠️ 🚨