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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
A new Fn::Range intrinsic function, which would take in either 1 or 2 integer parameters, and would return the corresponding range of integers in String format.
Tell us about the problem you are trying to solve. What are you trying to do, and why is it hard?
Have multiple CommaDelimitedList parameters that I would like to reference within the Resources I create in the Fn::ForEach intrinsic function (see example below). If this function exists, can leverage this and the Fn::Length intrinsic function to achieve what I want.
I'd have to define a Mappings section with the corresponding mapping between the list of parameters that would be iterated over, and the other parameter values for the other properties I've defined.
Note: an alternative solution to this could be Item 2 in #118
What is the expected behavior with this new feature
Community Note
Tell us about your request
A new
Fn::Range
intrinsic function, which would take in either 1 or 2 integer parameters, and would return the corresponding range of integers in String format.Tell us about the problem you are trying to solve. What are you trying to do, and why is it hard?
Have multiple CommaDelimitedList parameters that I would like to reference within the Resources I create in the Fn::ForEach intrinsic function (see example below). If this function exists, can leverage this and the Fn::Length intrinsic function to achieve what I want.
Are you currently working around this issue?
I'd have to define a Mappings section with the corresponding mapping between the list of parameters that would be iterated over, and the other parameter values for the other properties I've defined.
Note: an alternative solution to this could be Item 2 in #118
What is the expected behavior with this new feature
Want to be able to do something like this:
The text was updated successfully, but these errors were encountered: