jkleinlercher
commented
4 years ago it seems, if the configuration object we need to change is an item in a list, we would need to
- first get all items of one configuration type
- then iterate over every item
- check if the name is already listed (then we know the object is already created)
- get the id of the existing object
- then we can call the PUT method on this object.
However, not all configuration objects are list items (like tags, alerting-profiles, dashboards, kubernetes credentials, ...), some are also just base configurations (services anomaly detection, https://www.dynatrace.com/support/help/extend-dynatrace/dynatrace-api/configuration-api/anomaly-detection-api/anomaly-detection-api-services/)
changing configuration with PUT method is idempotent (like changing service anomaly detection with https://www.dynatrace.com/support/help/extend-dynatrace/dynatrace-api/configuration-api/anomaly-detection-api/anomaly-detection-api-services/put-config/). however, creating new objects with a POST method is not idempotent (like creating a new tag https://www.dynatrace.com/support/help/extend-dynatrace/dynatrace-api/configuration-api/automatically-applied-tags-api/post-auto-tag/)
since we need a general way to describe the desired state we either check if the object already exists in our tool or we discuss the API with dynatrace.