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
Is your feature request related to a problem? Please describe.
When deploying in an Azure tenant with a security policy that prohibits functions being accessible over http, the deployment fails.
Describe alternatives you've considered
As a workaround we created a fork of the project and updated the deployment JSON with the change as well as an edit in the shell script to point to our fork's JSON file, then pointed the deployment command to this fork's script location. This worked successfully but requires manually keeping up with merging changes to ensure these two files are kept in sync with upstream.
The text was updated successfully, but these errors were encountered:
Hello, thanks for pointing this out. Currently, the ownership of this component is in transition (not releasing new changes in November, at least, because even for quick fixes, testing is required). So, I created a ticket (PCLOUDS-5325) for it.
Is your feature request related to a problem? Please describe.
When deploying in an Azure tenant with a security policy that prohibits functions being accessible over http, the deployment fails.
Describe the solution you'd like
Update
dynatrace-azure-log-forwarder/deployment/dynatrace-azure-forwarder.json
Line 476 in 6625d36
"httpsOnly": true
.Describe alternatives you've considered
As a workaround we created a fork of the project and updated the deployment JSON with the change as well as an edit in the shell script to point to our fork's JSON file, then pointed the deployment command to this fork's script location. This worked successfully but requires manually keeping up with merging changes to ensure these two files are kept in sync with upstream.
The text was updated successfully, but these errors were encountered: