-
Notifications
You must be signed in to change notification settings - Fork 4k
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
(aws-cdk-lib.Fn): Support Fn::ForEach #27211
Comments
Thank you for the feature request and PR! This is an awesome feature! |
Giving this more thoughts, we'll have to think off how the interface would be. This could be applied to resources, conditions and outputs. |
Here's two different possibilities, we could create resources for it:
It would be nice to gather more input from CDK core members. |
This feature request is open for quite a while... any prevision on when it is coming? |
This is a feature we would really like to see. We have stacks that fetch parameters in remote regions using an AwsCustomResource and we want to be able to do Fn.split and then Fn.forEach to loop over them when CloudFormation executes. |
This is such a key to our business nowadays. It would be good if this gets prioritized. For us, we want to iterate over a parameter whose type is a list |
hey @faridnsh , I personnally am in favour of the first suggestion. It feels more typescripty and less yamlish. |
The first suggestion is indeed more typescripty and that's precisely why it shouldn't be implemented that way. We have to note that CDK is used in many languages, and, IMO, it should have a good experience in all of them :) |
Have the same use case |
Describe the feature
Fn::ForEach is a new function that is added to cloudformation.
Use Case
Creating multiple resources based on Cloudformation template parameter. I'm deploying CDK generated templates to Service Cataloge.
Proposed Solution
ForEach function in aws-cdk-lib.Fn
Other Information
No response
Acknowledgements
CDK version used
v2.96.2
Environment details (OS name and version, etc.)
Any
The text was updated successfully, but these errors were encountered: