fix(pipelines): propagate CodeBuild fleet and certificate

[isker]

Issue # (if applicable)

Closes #35664.

Reason for this change

You can't use Fleets or certificates currently in CDK pipelines.

Description of changes

These properties were simply overlooked. I added a TypeScript satisfies assertion to ensure that newly added properties are not missed here.

Describe any new or updated permissions being added

N/A

Description of how you validated changes

Unit and integration tests.

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

[leonmk-aws]

@isker Can you merge from main and resolve the conflicts ?

[isker]

I will do that, but is it going to then sit for another two months without a review? Contributing to this project is pretty demoralizing in this regard.

[github-actions]

	Tests	Passed ☑️	Skipped	Failed ❌️
Security Guardian Results	26 ran	24 passed		2 failed

Test	Result
Security Guardian Results
packages/@aws-cdk-testing/framework-integ/test/pipelines/test/integ.pipeline-with-variables.js.snapshot/VariablePipelineStack.template.json
iam-no-wildcard-actions-inline.guard	❌ failure
s3-encryption-enabled.guard	❌ failure

• View Security Guardian Results

[github-actions]

	Tests	Passed ☑️	Skipped	Failed ❌️
Security Guardian Results with resolved templates	26 ran	24 passed		2 failed

Test	Result
Security Guardian Results with resolved templates
packages/@aws-cdk-testing/framework-integ/test/pipelines/test/integ.pipeline-with-variables.js.snapshot/VariablePipelineStack.template.json
iam-no-wildcard-actions-inline.guard	❌ failure
s3-encryption-enabled.guard	❌ failure

• View Security Guardian Results with resolved templates

[leonmk-aws]

Thank you for your merging from main (without this I cannot merge the PR), for your patience and for the longterm fix to prevent this from happening in the future !

[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]

Merge Queue Status

🚫 The pull request has left the queue (rule: default-squash) at 260cc05

This pull request spent 4 seconds in the queue, with no time running CI.

Reason

The pull request can't be updated

For security reasons, Mergify can't update this pull request. Try updating locally.
GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/security-guardian.yml without workflows permission

Hint

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

Pull request has been modified.

[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]

Merge Queue Status

✅ The pull request has been merged at fc0e79b

This pull request spent 35 minutes 20 seconds in the queue, including 35 minutes 11 seconds running CI.
The checks were run in-place.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • fix(pipelines): propagate CodeBuild fleet and certificate #35673
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • fix(pipelines): propagate CodeBuild fleet and certificate #35673
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

[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.