ci(integration-test-deployment): bootstrap account before deployment

[Abogical]

Reason for this change

For integration deployment tests, accounts under atmosphere do not have the CDK bootstrap.

Description of changes

Add a bootstrap step to the integration deployment test.

Describe any new or updated permissions being added

No new IAM permissions added.

Description of how you validated changes

Workflow runs successfully under fork: https://github.com/Abogical/aws-cdk/actions/runs/18687737855/job/53284876440

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[kumvprat]

Couple of questions :

• Why not bootstrap these accounts from start and avoid the whole bootstraping for each integ test?
• Is there a way to check if the account is already bootstrapped and avoid executing this command ?

[Abogical]

@kumvprat

Couple of questions :

• Why not bootstrap these accounts from start and avoid the whole bootstraping for each integ test?
• Is there a way to check if the account is already bootstrapped and avoid executing this command ?

• Atmosphere is supposed to remove the bootstrap from the account automatically when it is deallocated.
• Yes, however the cost is minimal even if we try to deploy the bootstrap again. As cloudfromation will detect that the stack is already deployed and won't do anything.

[kumvprat]

LGTM

--disable-update-workflow seems to be a requirement since the integ runner looks for main branch 🤷

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[Abogical]

FYI on --disable-update-workflow: The update workflow did not work as the integ runner does not find the 'main' branch within the workflow environment. See this example in the logs of a previous run: https://github.com/Abogical/aws-cdk/actions/runs/18650693435/job/53281026995#step:13:212

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[Abogical]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.