Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

credential scopes discussion

See original GitHub issue

All languages should be able to support a list of credential scopes (with flag --credential-scopes), so users won’t have to pass credential scopes themselves. Agree with @lmazuel that in ARM mode, we should default the credential scope to https://management.azure.com/.default, since that’s always the case for ARM mode.

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:6 (6 by maintainers)

Top GitHub Comments

2reactions

iscai-msftcommented, Jan 28, 2021

yep! currently some languages are doing this themselves, go into it a little bit in the credential-scopes section of flag docs. Since there’s this different behavoir and we want unified, would be nice for autorest core to handle it.

side note: if users input --azure-arm --credential-scopes=myscopes, we should respect their inputted credential scopes and not override to https://management.azure.com/.default.

0reactions

iscai-msftcommented, Feb 2, 2021

@jianghaolu didn’t think about having a parameterized credential scope. I like the idea of adding /.default to the end of credential scopes and warning users this is what we’re doing. It seems like a good default 😉