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

AzOps - Pull failing on AzOps 1.8.0 #639

Closed
CerveloRS opened this issue May 24, 2022 · 6 comments · Fixed by #640
Closed

AzOps - Pull failing on AzOps 1.8.0 #639

CerveloRS opened this issue May 24, 2022 · 6 comments · Fixed by #640
Labels

Comments

@CerveloRS
Copy link

AzOps - Pull pipeline was running withouth the version parameter set and started failing when 1.8.0 became the latest release.

Steps to reproduce

  1. Run AzOps - Pull pipeline with version 1.8.0 of AzOps module.

Screenshots
image

Workaround
Force AzOps - Pull pipeline to use version 1.7.7

@daltondhcp
Copy link
Contributor

daltondhcp commented May 24, 2022

Thank you for reporting this. It is not something we have seen in any of our tests or other environments so far.
Can you please share your settings.json file as well as execution environment (GitHub actions/Azure DevOps) and if you are using self-hosted runners?

@CerveloRS
Copy link
Author

  • Settings.json attached.
  • Environment: Azure Devops
  • Not using self hosted

settings.zip

@Jefajers
Copy link
Member

Thanks for your quick reply, we are looking into it.

We are able to reproduce this when Core.PartialMgDiscoveryRoot is set.

@CerveloRS
Copy link
Author

Thank you!

@daltondhcp
Copy link
Contributor

daltondhcp commented May 24, 2022

Thank you again for reporting this @CerveloRS - this is now fixed in our 🚒 release 1.8.1.
Please let us know if something isn't working as expected. To ensure this doesn't happen again, we will ensure to expand our automated test cases to include Core.PartialMgDiscoveryRoot in #641

@CerveloRS
Copy link
Author

Thank you. Confirmed working on my end aswell.
Great work :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants