Hello Folks,
Due to the end of life of Python 3.10, we need to upgrade our extensions to supported versions that use Python 3.13 or later.
As part of this effort, several of our existing extensions also need to be upgraded. During our assessment, we identified a number of extensions with the "com.dynatrace" prefix that require updates as well.
These extensions were developed in collaboration with Dynatrace, and I assume the naming convention is consistent across organizations for customer-specific extensions developed by Dynatrace.
We use Visual Studio Code to upgrade and deploy these extensions. However, the upgraded extensions must be renamed with the "custom:" prefix, which causes Dynatrace to treat them as entirely new extensions during deployment. Since these are locally developed extensions, we also need to generate a new pair of developer.pem and root.pem certificates.
For ActiveGate extensions, the process is relatively straightforward, as they only need to be uploaded to the ActiveGates. The real challenge arises with OneAgent extensions, which must be deployed across all hosts. This makes the process significantly more complex and time-consuming.
My question is: Is there any way to bypass this certificate verification requirement? Deploying and maintaining certificates across a large number of hosts would be operationally challenging and would add considerable overhead to the upgrade process.
Regards,
AK
