awslabs/aws-service-catalog-puppet

Launch constrains are not applied after update to 0.246.0

Opened this issue · 2 comments

naspinec commented

Describe the bug
Launch constrains are not applied after update to 0.246.0

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
Have launch constrains applied to products associated to portfolios.

Attachments
Please attach a copy of your manifest, expanded-manifest, logs and build artefacts where appropriate.
manifest.yaml.txt
manifest-expanded.yaml.txt
CreateAssociationsForSpokeLocalPortfolioTask-CreateAssociationsForSpokeLocalPortfolioTask_515411312103___arn_aws_iam______spoke_local_po_317fd571b4.json.txt
CreateLaunchRoleConstraintsForSpokeLocalPortfolioTask-CreateLaunchRoleConstraintsForSpokeLocalPortfolioTask_006805366288___spoke_local_po____products______81075ad8e1.json.txt
puppet-run-logs.zip

eamonnfaherty commented

the current version assumes each portfolio will only be shared once via a single spoke-local-portfolio

This is not aligned to how the solution is being used.

eamonnfaherty commented

same issue will affect resource update constraints