Closed mataness closed 3 years ago
Thank you for your feedback. Tagging and routing to the team members best able to assist.
As a workaround, the IMDS endpoint host can now be configured via environment variable. https://github.com/Azure/azure-sdk-for-net/blob/72630d5bb04538967195c199632d8260133d25e5/sdk/identity/Azure.Identity/src/EnvironmentVariables.cs#L21
Not sure why it's closed, overriding the environment variable is not a clean design. Why not exposing this functionality as a constructor parameter?
Hi @mataness - We'll consider this a feature request and monitor the issue to see if there is more demand for this feature.
If I want to contribute and submit a PR to support this functionality, will you allow it ?
If I want to contribute and submit a PR to support this functionality, will you allow it ?
We're happy to accept contributions. How were you planning to implement this?
ManagedIdentityCredential
What do you think? should I go ahead and implement this ?
In Azure.Identity NuGet, the implementation of ManagedIdentityCredential implicitly selecting the ManagedIdentitySource (e.g. IMDS, ServiceFabric).
In my scenario, we have both IMDS and ServiceFabric managed identities available for the process. However, in some cases I want that my application will use ServiceFabricManagedIdentitySource and in some other cases I want to use the IMDS source.
Is it possible to add additional constructor to ManagedIdentityCredential that will force choosing the managed identity source?