- Le plus récent
- Le plus de votes
- La plupart des commentaires
If you need to modify the CI/CD pipeline itself (e.g., changes to the CodePipeline configuration in the codepipeline.yaml file), your steps are correct. 1)Editing the codepipeline.yaml. 2)Commit and push the changes to CodeCommit. 3) Run sam deploy -t codepipeline.yaml --stack-name sam-app-pipeline --capabilities=CAPABILITY_IAM. If you encounter errors, especially due to breaking changes in the pipeline, deleting the CI/CD stack (sam-app-pipeline) and redeploying is a reasonable approach When you delete the stages or the entire CI/CD pipeline stack, you're correct that you should be left with the Cloud9 environment and the CodeCommit repository. There should not be any hidden leftovers from the old version if you've properly deleted the relevant CloudFormation stacks. Deleting the CI/CD stack (sam-app-pipeline) should remove all associated resources, however, it's always a good practice to verify the AWS Management Console or use AWS CLI commands to ensure that no unexpected resources are left behind Remember to test your pipeline changes in a safe environment before applying them to production, and regularly review AWS resources to avoid any unexpected leftovers.
Hope it clarifies and if does I would appreciate answer to be accepted so that community can benefit for clarity, thanks ;)
Contenus pertinents
- demandé il y a un mois
- demandé il y a 10 mois
- demandé il y a 19 heures
- demandé il y a 3 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 3 ans