Support for private/air gapped cloud environments

[amirschw]

It would be great if the exporter could support private/airgapped clouds.

To do that, we can introduce a new AZURE_RESOURCE_MANAGER_ENDPOINT flag (and AZURE_GRAPH_ENDPOINT, if graph is also used). Looking at the codebase, it seems that the change is not that straightforward given the dependency on the armclient package.

[mblaschke]

let me think about a general way for overwriting cloud endpoints.
This might be easier for the new armclient and in the old SDK.

[mblaschke]

in worst case it could mean to pass an environment variable eg AZURE_CLOUD_CONFIG with a json configuration for all services.

[mblaschke]

please try docker image webdevops/azure-resourcemanager-exporter:main (when/if build is finished)
with following env vars:

AZURE_ENVIRONMENT=AzurePrivate
AZURE_CLOUD_CONFIG='{"activeDirectoryAuthorityHost":"https://login.microsoftonline.com/","services":{"resourceManager":{"audience":"https://management.core.windows.net/","endpoint":"https://management.azure.com"}}}'

and adapt accordingly

documented here: https://github.com/webdevops/go-common/tree/main/azuresdk

thinking also about AZURE_CLOUD_CONFIG_FILE so the cloudconfig could be passed as path 🤔

[amirschw]

Thanks a lot, I'll give it a try!

+1 for passing a path to the config file

[mblaschke]

Are you having the AzureAD also on-premise or are you using public AzureAD?

[amirschw]

Yes, I am using a different instance of Azure AD, not the public one.

[mblaschke]

with newest :main version you have two options:

specify the cloud config via AZURE_CLOUD_CONFIG as string or AZURE_CLOUD_CONFIG_FILE as file path

content should be:

{
    "activeDirectoryAuthorityHost": "https://login.microsoftonline.com/",
    "services": {
        "resourceManager": {
            "audience": "https://management.core.windows.net/",
            "endpoint": "https://management.azure.com"
        },
        "microsoftGraph": {
            "audience": "https://graph.microsoft.com",
            "endpoint": "https://graph.microsoft.com"
        }
    }
}

adapt endpoints accordingly

this solution will be build in every azure exporter as soon they are migrated to the new azure-sdk-for-go version.

[mblaschke]

Please reopen if there are still issues