SCT Puppet Pipeline Failed while deploying products with TagOption Enabled

[shydhanya]

Reopening - Launches are not respecting tag options #611 - I have tested this by manually associating tagOptions to existing portfolio and redployed successfully using puppet options. Existing product was not updated with Tags from TagOptions. However, terminating and recreating product worked.

Next step is to create tag options in factory and deploy via puppet.

Steps to reproduce

1. create a portfolio using factory that has tag options
2. set tag options sharing to true
3. provision a product in a spoke via a launch

Expected results

1. provisioned product should have tags from tag options

Actual results

1. Puppet Pipeline failed during deployment

Error Logs : Portfolio & Product listed in error logs are available

[eamonnfaherty]

At the moment the only support for tag options is when you have created and applied them before provisioning. Are you trying to do something else?

[shydhanya]

Thanks Eamonn. Upgraded to latest version 0.213. I have successfully launched (mandatory)products with TagOptions while provisioning for first time.

However, spoke-local-portfolios (elective) products deployment has missing TagOptions in both spoke portfolios and products.

spoke-local-portfolio with missing TagOptions -

manifest.yaml

Note: Imported tab has TagOption available in both products and portfolios.

[eamonnfaherty]

this is a dupe of this #612