-
Notifications
You must be signed in to change notification settings - Fork 3.8k
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Extend/remove the limit of 25 context after login #9865
Comments
@shaqian thanks for the suggestion -- is there a preference on how this should be implemented? I think there are two ways to go about this: (1) (2) Do you think it would be better to (1) create a context for every subscription that the user has access to, or (2) allow the user to provide how many contexts they want? |
Hi @cormacpayne I think 1) is better. :) |
@BethanyZhou , given we have no environment to accurately evaluate performance impact in large tenant, let's focus on option 2 for the time being. recommended parameter name is |
PR merged #12397 |
Description of the new feature
By default Azure PowerShell populates context for only 25 subscriptions after login.
https://github.com/Azure/azure-powershell/blob/master/src/Accounts/Accounts/Models/RMProfileClient.cs#L293
The limit is hard-coded. Users have to manually run additional commands to add more subscriptions.
It'd be great to have a more flexible way for user to choose how many subscriptions to populate context for.
Proposed implementation details (optional)
Add an option for how many context to populate by default.
The text was updated successfully, but these errors were encountered: