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

Deployment fails when the password contains a special character #180

Closed
mcooley opened this issue Jun 18, 2021 · 2 comments
Closed

Deployment fails when the password contains a special character #180

mcooley opened this issue Jun 18, 2021 · 2 comments

Comments

@mcooley
Copy link

mcooley commented Jun 18, 2021

The deploy.ps1 script passes a "botAppPassword" value to Azure CLI during deployment. The auto-generated password can contain quote ', ampersand &, and other special characters. When these special characters are present, there are unexpected errors during deployment.

Some of the symptoms I saw included errors like (password fragement) is not recognized as an internal or external command, operable program or batch file. and The system cannot find the path specified.

Azure CLI in PowerShell generally has issues quoting parameter values, as described here. That documentation mentions that one solution might be to format the parameters as JSON and use file input.

@mcooley mcooley changed the title Deployment fails when the password contains a quote character Deployment fails when the password contains a special character Jun 18, 2021
@SubbaReddi
Copy link

@mcooley: I don't see possibility to generate secret key value with special characters quote ', and ampersand &.
It contains majorly following characters only: ., -, _, ~

Based on following reference, some special characters were removed. So, can you confirm if you are able to generate new secret value with quote and ampersand.

@mcooley
Copy link
Author

mcooley commented Jun 28, 2021

I did some more research, and passwords generated with special characters was a bug in Azure CLI.

Updating Azure CLI to the latest version fixed the issue.

@mcooley mcooley closed this as completed Jun 28, 2021
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

No branches or pull requests

2 participants