feat: Adding new datadog monitors chart #347
Conversation
| # -- (`map[string]interface{}`) Optional: monitor options | ||
| options: |
There was a problem hiding this comment.
I would ignore all the sub-keys here and just point to the upstream documentation instead as we are not likely to keep this list up to date.
There was a problem hiding this comment.
It's an option I thought about for the whole thing, in theory the names and the structure is exactly the same as the CRD - I could in theory point out to the CRD(though some of the info was not properly documented and I had to extract it from the code).
| # -- (`map[string]interface{}`) Required: monitor resource name, Required unique monitor resource name(needed to allow value overrides and used a datadog monitor resource name) | ||
| resourceName: |
There was a problem hiding this comment.
I would not create a real entry here and instead just have a large comment block. (Although I see you have disabled the entry below so I dont have strong opinions on this.)
There was a problem hiding this comment.
That was my original intention, but couldn't figure out how to properly format it so that helm-docs recognize the fields....
Adding new datadog monitors chart to allow users to use it as a subchart and manage datadog alerts via the datadog CRD's.