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.

Sign up for GitHub

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

Jump to bottom

Manual TagOption association to Portfolio/Product created by SCT #621

Open
shydhanya opened this issue Jan 9, 2023 · 1 comment
Open

Manual TagOption association to Portfolio/Product created by SCT #621

shydhanya opened this issue Jan 9, 2023 · 1 comment

Comments

@shydhanya
Copy link

Manually add TagOptions in AWS Service Catalog in Puppet account.

Steps to reproduce

  1. Create TagOptions manually in AWS Service Catalog
  2. Associate the TagOption to Portfolio/Puppet
  3. Launch the product in child account

Expected results

Puppet pipeline should execute successfully and associate TagOptions to child accounts.

Actual results

Puppet execution failed to recognize the manual tagOption association while launching the product.
image

TagOption Configuration in AWS Service Catalog

image
@shydhanya
Copy link
Author

Any update on this? I have deleted the s3 artifacts and exeucted puppet pipeline successfully to release the lock issue. However, the puppet still didnt retain the TagOptions in spoke accounts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@shydhanya