Add Support for Datadog Powerpacks #1875
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds support for generating
datadog_powerpack
resources via.powerpack
.datadog_powerpack
is documented here.I've had the best luck either filtering for a specific set of powerpack ids (visible in dashboard json) like the following...
... or by filtering down using the "Search Categories". Example, if I configure search category "process", I can filter down to powerpacks with that search category with this filter...
I chose to use ListPowerpacksWithPagination, as I noticed that ListPowerpacks appears to set a default to 25 records. I don't see where this is configured. ListPowerpacksWithPagination seemed cleaner to use to me, as it manages page offsets.
This feature was requested in #1841.