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
Once we have for each we can generate resources in easy way, then usually we want to have them in monitoring dashboard.
But dashboard body is a far away from being friendly. We need to declare the same view N times..
Community Note
Tell us about your request
Once we have for each we can generate resources in easy way, then usually we want to have them in monitoring dashboard.
But dashboard body is a far away from being friendly. We need to declare the same view N times..
But also we have toJsonString and join
So I want point the need to have dashboard body like (pseudo code)
There is also alternative - to dynamic
dashboard body item
resource.Are you currently working around this issue?
Currenlty I have ugly yaml that describe dashboard transformed with Fn:ToJsonString...
What is the expected behavior with this new feature
The expected behavior is to have possibility of the Cloudwatch dashboard body generation through for each.
The text was updated successfully, but these errors were encountered: