You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In @aws-cdk/pipelines, currently each stage is deployed with a Prepare-Step ( Cloudformation CHANGE_SET_REPLACE) and
a Deploy Step (CHANGE_SET_EXECUTE action). We often have the case, that a change set is empty. In this case, the deploy step only takes a second, but the prepare step takes more than 60s to prepare an empty change set. Customer Support found out that this due to the many API calls being made:
CP workers first describe the change set using DescribeChangeSet, ensure to delete if a change set exists with the same name using DeleteChangeSet call, create the change set using CreateChangeSet API call. In this workflow, majority of time is elapsed between the DescribeChangeSet & DeleteChangeSet; and 'CreateChangeSet&DescribeChangeSet` calls.
Apparently, they are aware of the issue and have a (low priority) ticket to improve that speed. There might be a good workaround, though, if we could use the Create or Update stack action mode:
`in case of Create or Update stack action mode, CP workers try to directly update the CFN using UpdateStack API call, but fails with error: "No updates are to be performed
So if we had an option to use aws-cdk-lib.aws_codepipeline_actions.CloudFormationCreateUpdateStackAction under the hood of pipelines, it would greatly improve the speed of our pipelines until the codepipeline team has dealt with that issue.
What do you think. Could that be an option?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In @aws-cdk/pipelines, currently each stage is deployed with a
Prepare-Step
( CloudformationCHANGE_SET_REPLACE
) anda
Deploy Step
(CHANGE_SET_EXECUTE
action). We often have the case, that a change set is empty. In this case, the deploy step only takes a second, but the prepare step takes more than 60s to prepare an empty change set. Customer Support found out that this due to the many API calls being made:Apparently, they are aware of the issue and have a (low priority) ticket to improve that speed. There might be a good workaround, though, if we could use the
Create or Update stack action mode
:So if we had an option to use
aws-cdk-lib.aws_codepipeline_actions.CloudFormationCreateUpdateStackAction
under the hood of pipelines, it would greatly improve the speed of our pipelines until the codepipeline team has dealt with that issue.What do you think. Could that be an option?
Beta Was this translation helpful? Give feedback.
All reactions