awscc - cloudformation hook execution mode #7126
Draft
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.
CloudFormation hooks execute like other cfn extensions, execute in a fairly strange world, where they are executed on instances, in the CloudFormation service account, and have to juggle credentials both into the customer/user account and the service account. It smells like a poorly reinvented lambda in terms of packaging with zip files in zip files and extraneous json files with duplicative metadata.