Open jkleinlercher opened 4 years ago
I will export every config object of my trial account to https://github.com/rockaut/dynatrace-config/tree/master/experiments/config and try to get a better feeling how every API works.
since issue #1 is implemented for most of the configuration objects I now know that return codes and http method are pretty straight forward, so they don't need to get specified in the json files anymore. I will definitely need to test now every configuration API with the current version of this program to get a better understanding what works and what not. Outcome of this task should be a summary of problems and confusions.
status of test: done:
next steps: all APIs dealing with list items:
more complex APIs:
all new api tests go to feature/#2 branch
we need to better understand the general anatomy/behaviour of the dynatrace APIs.
Until now I did not know if successful return codes are always HTTP 204 and if the http method is always PUT, or sometimes POST. Now it seems that every successful return code is HTTP 204. And if we find out in issue #1 that the http method is always PUT with the evaluated ID of the existing object (except if the object doesn't exist, it is a POST), then we can remove the method and success keys in the config json files.