[tool]update llc-quick-start-tool for py3 only #22507
Conversation
msyyc
commented
Jan 14, 2022
•
msyyc
commented
|
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
|
/check-enforcer override |
…into merge_patch * 'main' of https://github.com/Azure/azure-sdk-for-python: (72 commits) [tool]update llc-quick-start-tool for py3 only (Azure#22507) [mgmt] update setupy for python3.6 (Azure#22505) [pipeline] Upgrade python version to `python3.8` (Azure#22503) [AutoRelease] t2-synapse-2022-01-11-70733 (Azure#22439) Update tests.md (Azure#22500) disable per Azure#22498 (Azure#22499) [AnomalyDetector] Release 3.0.0b4 (Azure#22191) [translation] update docs to include managed identity option (Azure#22366) add back py3.6 (Azure#22478) Add Python 3.6 support back to Storage packages (Azure#22483) allow Python 3.6 with the sdk (Azure#22456) remove hardcoded subscription ID (Azure#22481) clean up tests/docs (Azure#22480) Increment version for eventhub releases (Azure#22485) [Cosmos] Remove support for Python27, set Python36 as minimum, and update cosmos emulator pipeline (Azure#22475) Increment version for servicebus releases (Azure#22484) add back py3.6 (Azure#22477) [AutoRelease] t2-datafactory-2022-01-06-31864 (Azure#22362) [AutoRelease] t2-apimanagement-2022-01-06-51326 (Azure#22361) [AutoRelease] t2-netapp-2022-01-12-75881 (Azure#22467) ...
…into add_back_error_message * 'main' of https://github.com/Azure/azure-sdk-for-python: (127 commits) [tool]update llc-quick-start-tool for py3 only (Azure#22507) [mgmt] update setupy for python3.6 (Azure#22505) [pipeline] Upgrade python version to `python3.8` (Azure#22503) [AutoRelease] t2-synapse-2022-01-11-70733 (Azure#22439) Update tests.md (Azure#22500) disable per Azure#22498 (Azure#22499) [AnomalyDetector] Release 3.0.0b4 (Azure#22191) [translation] update docs to include managed identity option (Azure#22366) add back py3.6 (Azure#22478) Add Python 3.6 support back to Storage packages (Azure#22483) allow Python 3.6 with the sdk (Azure#22456) remove hardcoded subscription ID (Azure#22481) clean up tests/docs (Azure#22480) Increment version for eventhub releases (Azure#22485) [Cosmos] Remove support for Python27, set Python36 as minimum, and update cosmos emulator pipeline (Azure#22475) Increment version for servicebus releases (Azure#22484) add back py3.6 (Azure#22477) [AutoRelease] t2-datafactory-2022-01-06-31864 (Azure#22362) [AutoRelease] t2-apimanagement-2022-01-06-51326 (Azure#22361) [AutoRelease] t2-netapp-2022-01-12-75881 (Azure#22467) ...
* update for py3 only * Update setup.py
{AzureConsumption} fixes Azure/azure-rest-api-specs#22446 tiny typo in description (Azure#22507)
In the Usage Details - List documentation for the Consumption Api the "scope" parameter contains the following (reformatted for ease of reading):
Also, Modern Commerce Account scopes are:
'/providers/Microsoft.Billing/billingAccounts/{billingAccountId}' for billingAccount scope,
'/providers/Microsoft.Billing/billingAccounts/{billingAccountId}/billingProfiles/{billingProfileId}' for billingProfile scope,
'providers/Microsoft.Billing/billingAccounts/{billingAccountId}/billingProfiles/{billingProfileId}/invoiceSections/{invoiceSectionId}' for invoiceSection scope, and
'providers/Microsoft.Billing/billingAccounts/{billingAccountId}/customers/{customerId}' specific for partners.
The uri templates in the last two patterns *don't" start with a forward slash.
