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
in the Dynatrace UI, it is possible to order the list of process group naming rules. There are buttons for moving a rule up or down in. I assume this defines in which order the rules are applied at runtime.
How is it possible to do this in Terraform when defining multiple processgroup_naming resources?
Thanks a lot for your advice!
The text was updated successfully, but these errors were encountered:
The resource dynatrace_processgroup_naming is backed by a REST API that currently doesn't allow for ordering them.
The WebUI utilizes the schema builtin:naming.processes-and-containers of Settings 2.0 (offers ordering by default) - which hasn't been made available for the public for various reasons.
I've reached out to R&D about an ETA for when that new schema will be available for the public. Responses so far sounded a bit like there was no awareness about the functionality gap here.
As soon as ordering these settings via REST calls will be available the provider will adopt that, for sure. I'll keep that ticket open for a bit longer, until I have some concrete answers from R&D.
There seems to exist an undocumented endpoint for ordering process group naming rules:
PUT https://#####.live.dynatrace.com/api/config/v1/conditionalNaming/processGroup/order
Similar to the idea suggested in #582 for Custom Services we may be able to achieve the same goals for process group namings.
We need to reach out to Dynatrace R&D about whether utilizing that URL is safe/future proof.
Hi everyone,
in the Dynatrace UI, it is possible to order the list of process group naming rules. There are buttons for moving a rule up or down in. I assume this defines in which order the rules are applied at runtime.
How is it possible to do this in Terraform when defining multiple processgroup_naming resources?
Thanks a lot for your advice!
The text was updated successfully, but these errors were encountered: