-
Notifications
You must be signed in to change notification settings - Fork 150
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
Support AZURE_CONFIG_DIR #673
Comments
As far as I can tell, the Maven plugin uses
It might be feasible to replace that with a helper method that looks up Alternatively, it might be a good idea to expose the path as Maven property. |
FWIW, I created a quick hack and opened PR #674 for this issue. I hope that is okay. |
@alexandrospanagiotidis Thanks for your report and your contribution! Maven Plugin use Codes which refers |
Hi @Flanker32, thank you for your reply. Should I delete my PR, since this is something that needs to be fixed via the other issue? |
@alexandrospanagiotidis Yes, thanks for your support, I'll track this issue and fixed it once the related one is done. |
Hi @alexandrospanagiotidis, we have already solve this issue by adopting azure-identity, could you please take a try again. |
Dear @andxu, Thank you for your reply! I am no longer able to test your changes, as I am no longer involved in that particular project. As a side-note: we moved away from deploying via Thank you for your efforts! All the best |
Plugin name and version
azure-webapp-maven-plugin 1.6.0
Plugin configuration in your
pom.xml
Expected behavior
The Maven plugin uses the right configuration directory, set via
AZURE_CONFIG_DIR
as described in the documentation for Azure CLI.Actual behavior
The plugin always uses the configuration in
$HOME/.azure
if present.If that is missing, an error is thrown:
Steps to reproduce the problem
$HOME/.azure
is missing (e.g., move it away, or delete it)AZURE_CONFIG_DIR
to something else than$HOME
, e.g.,export AZURE_CONFIG_DIR="$(mktemp)"
(under Linux in a Bash)mvn azure-webapp:deploy
The text was updated successfully, but these errors were encountered: