Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service catalog puppet deploy run superseeded #391

Open
RichMerritt opened this issue Jul 8, 2021 · 0 comments
Open

Service catalog puppet deploy run superseeded #391

RichMerritt opened this issue Jul 8, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@RichMerritt
Copy link

Please include a link to your expanded manifest, the full contents of your AWS CodeBuild output (see https://aws-service-catalog-puppet.readthedocs.io/en/latest/puppet/using_the_cli.html#export-puppet-pipeline-logs)

Please ensure you are using the latest version and have run a validate command on your manifest file see (https://aws-service-catalog-puppet.readthedocs.io/en/latest/puppet/using_the_cli.html#validate)

Steps to reproduce

  1. Vend an account with Service Catalog - account is vended
  2. Parameterized source file updated with account id to trigger puppet pipeline
  3. Update manifest.yaml and commit to trigger puppet pipeline concurrently

Expected results

Account is vended and correctly boostrapped by puppet

Actual results

Puppet pipeline deploy phase that was triggered by account vend is superseeded by the pipeline that was triggered in step 3 and account is not correctly boostrapped as per behaviour of codepipeline: https://docs.aws.amazon.com/codepipeline/latest/userguide/concepts-how-it-works.html#concepts-how-it-works-executions

@eamonnfaherty eamonnfaherty added the enhancement New feature or request label Sep 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants