Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve declaration of Cloudwatch body. #133

Open
maciejGolebio opened this issue Aug 1, 2023 · 0 comments
Open

Improve declaration of Cloudwatch body. #133

maciejGolebio opened this issue Aug 1, 2023 · 0 comments

Comments

@maciejGolebio
Copy link

Community Note

  • 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..

But also we have toJsonString and join

So I want point the need to have dashboard body like (pseudo code)

body:
    Fn::Join:
	  - Fn:ToJsonString:
	        - Dashboard Title
		- Some non repeatable views
	  - For:each:Alarms:
		- AlarmName
		- - Ref! alarm1 
		  - Ref! alarm2
		- View for ${AlarmName}   

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant