Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow a new authorizer to be created from a configuration file by specifying a resource instead of a base url. #313

Merged
merged 1 commit into from
Sep 6, 2018

Conversation

nphmuller
Copy link
Contributor

This enables resource like KeyVault and Container Registry to use an authorizer configured from a configuration file.

…cifying a resource instead of a base url.

This enables resource like KeyVault and Container Registry to use an authorizer configured from a configuration file.
@marstr
Copy link
Member

marstr commented Sep 4, 2018

This is related to Azure/azure-sdk-for-go#2610

@nphmuller
Copy link
Contributor Author

@marstr
It's related to that issue, but it's not the solution to it.

This PR just allows the NewAuthorizerFromFile flow to be used with every resource.

Before the changes in this PR the only way to use this flow was by providing a baseurl, which was used to determine the resource url. Downside was that some resources like KeyVault cannot be determined this way (afaik), so I've basically provided an overload where the user can provide the resource url directly.

This overload already exists for the NewAuthorizerFromEnvironment flow.

@marstr marstr merged commit 60d22e3 into Azure:dev Sep 6, 2018
@nphmuller nphmuller deleted the NewAuthFromFileWithResource branch October 4, 2018 11:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants