You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using a StringList from replacements in Array field in other configs validation succeeds, but Prepare fails in the pipeline with:
* /reports/budgets/0/notifications/0/recipients/0 => must be string
* /reports/budgets/0/notifications/1/recipients/0 => must be string
* /reports/budgets/0/notifications/2/recipients/0 => must be string
* /reports/budgets/0/notifications/3/recipients/0 => must be string
To Reproduce
Create a variable in replacements-config.yaml:
Expected behavior
Validation succeeds and so should the pipeline.
Please complete the following information about the solution:
Version: [v1.9.2]
To get the version of the solution, you can look at the description of the created AWS CloudFormation stack used to install the LZA (AWSAccelerator-InstallerStack). For example, "(SO0199) Landing Zone Accelerator on AWS. Version 1.5.1.". If the description does not contain the version information, you can look at the Parameters of the stack for the RepositoryBranchName as that should contain the version number.
Region: [e.g. eu-west-1]
Was the solution modified from the version published on this repository? No
If the answer to the previous question was yes, are the changes available on GitHub?
Have you checked your service quotas for the services this solution uses?
Were there any errors in the CloudWatch Logs? No
Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
When using a
StringList
from replacements in Array field in other configs validation succeeds, butPrepare
fails in the pipeline with:To Reproduce
Create a variable in
replacements-config.yaml
:then use it in
global-config.yaml
:Expected behavior
Validation succeeds and so should the pipeline.
Please complete the following information about the solution:
Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: