You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When calling az devops login for the very first time, it installs pythons keyring package. For some reason that's not included in the default setup. This adds needless time to a first invocation of az devops login on the GitHub Hosted Runners and Azure Pipelines.
You can force the installation of keyring using
echo "dummy" | az devops login
az devops logout
On the GitHub/Azure Pipelines hosted runner the provisioning of the image happens on a non-interactive session and az devops login fails with an error along those lines.
ERROR: (1312, 'CredRead', 'A specified logon session does not exist. It may already have been terminated')
Unfortunatly, az devops doesn't provide a clean way to install keyring during installation or through a command other than catching the failed login.
Describe the solution you'd like
Either azdevops should preinstall keyring during normal installation of the extension. It's unclear why it's not included in the first place.
Or there should be a clean way to run az devops install-dependencies or something to have it download its dependencies in a provisioning scenario.
and it works. But since there is no way to grab the correct version of keyring from anywhere other than the sourcecode of az devops, it's a very brittle contract.
For now we're looking into just swallowing any message printed by az devops login. But that's of course also a brittle contract.
I know I could also set an environment variable with an access token instead of calling az devops login, unfortunately that also adds a 10 second delay on the GitHub Hosted Runner / Azure Pipelines runner as it tries to run az login, sees it fail and only then reverts to using the token supplied on the commandline.
The text was updated successfully, but these errors were encountered:
jessehouwing
changed the title
[Feature Request] Install Keyvault by default or offer a way to install keyvault without causing error messages
[Feature Request] Install keyring by default or offer a way to install keyring without causing error messages
Sep 28, 2023
Is your feature request related to a problem? Please describe.
When calling
az devops login
for the very first time, it installs pythons keyring package. For some reason that's not included in the default setup. This adds needless time to a first invocation ofaz devops login
on the GitHub Hosted Runners and Azure Pipelines.You can force the installation of keyring using
On the GitHub/Azure Pipelines hosted runner the provisioning of the image happens on a non-interactive session and
az devops login
fails with an error along those lines.Unfortunatly,
az devops
doesn't provide a clean way to install keyring during installation or through a command other than catching the failed login.Describe the solution you'd like
Either azdevops should preinstall keyring during normal installation of the extension. It's unclear why it's not included in the first place.
Or there should be a clean way to run
az devops install-dependencies
or something to have it download its dependencies in a provisioning scenario.I grabbed the following lines from the code:
and it works. But since there is no way to grab the correct version of keyring from anywhere other than the sourcecode of az devops, it's a very brittle contract.
For now we're looking into just swallowing any message printed by
az devops login
. But that's of course also a brittle contract.Additional context
I know I could also set an environment variable with an access token instead of calling
az devops login
, unfortunately that also adds a 10 second delay on the GitHub Hosted Runner / Azure Pipelines runner as it tries to runaz login
, sees it fail and only then reverts to using the token supplied on the commandline.The text was updated successfully, but these errors were encountered: