Reinhard-Pilz-Dynatrace
commented
3 days ago Hello @o6uoq
If the documentation of our REST APIs differs from the actual behavior, we need to apologize for the confusion.
The documentation of the Terraform Provider is essentially a mirror of the documentation of the API docs. The same thing applies to the documentation of the Pulumi Provider, which is at its core utilizing the Terraform Provider. Both Providers are pretty much parrotting what the API Docs are stating.
Reading through your comment it appears that there exists a bit of misunderstanding about the country code, though.
According to the documentation country code is the Alpha 2 code of the ISO 3166-2 standard. For Australia that is indeed AU. The FIPS 10-4 country code AS for Australia doesn't apply here.
Where I am with you is when it comes to the region code attribute. I've tested out manually what region code is getting generated when creating a couple of Private Synthetic Locations using the WebUI. Specifically for anything in London it appears that the region code ENG is being used here - which doesn't seem to relate in any way to FIPS. Similarly, when trying to create a Synthetic Location via API using the FIPS entry UKH9_407_414_city corporation____London, City of__ and following the documentation, the region code H9 is getting thrown back.
I've reached out to Dynatrace R&D about clarification here. Like you've written, there seems to exist some overlap with the FIPS 10-4 code but it is not clear to what extent.
Dynatrace states that they use FIPS 10-4 codes, but the API responses and API working logic says otherwise.
Where it says FIPS 10-4 is used:
That should imply that countries like Australia are AS, but AU is actually the correct country code respected by Dynatrace.
There's some use of FIPS e.g. region codes:
..but the same does not apply for all countries e.g:
Another example is London aka City of London, where they have come up with LND I have NFI.
The drift between Dynatrace documentation, Dynatrace APIs and reality is embarrassing. It circumvents standards, standards in which you proclaim to use, yet no documentation to validate the cross-breeding, hybrid mixmash that is how they currently define country + region codes.