We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Given Azure CLI is present and the user is authenticated. The nuke :secrets command could set the secret variable directly in Azure DevOps.
nuke :secrets
git@ssh.dev.azure.com:v3/<organization/<project>/<repo-name>
az pipelines list --organization <organization> --project <project>
az pipelines variable create --name <secret-name> --value <secret-value> --organization <organization> --project <project> --pipeline-name <pipeline>
See https://nuke.build/docs/global-tool/secrets/
No response
The text was updated successfully, but these errors were encountered:
done
Sorry, something went wrong.
No branches or pull requests
Description
Given Azure CLI is present and the user is authenticated. The
nuke :secrets
command could set the secret variable directly in Azure DevOps.Usage Example
See https://nuke.build/docs/global-tool/secrets/
Alternative
No response
The text was updated successfully, but these errors were encountered: