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

Add support for regional STS #19392

Merged
merged 9 commits into from
Jun 30, 2021
Merged

Add support for regional STS #19392

merged 9 commits into from
Jun 30, 2021

Conversation

chlowell
Copy link
Member

@chlowell chlowell commented Jun 22, 2021

... to sync client secret and certificate credentials (async support is blocked on #6354). Closes #19301

@check-enforcer
Copy link

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:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

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:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run python - [service] - ci

from msal import ConfidentialClientApplication


class RegionalAuthority(with_metaclass(CaseInsensitiveEnumMeta, str, Enum)):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a question: should this pattern be applied to all enums, all new enums, or only some?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All enums (see the guidelines). CaseInsensitiveEnumMeta is relatively new, so we've shipped many enums without it. Adding it to those should be non-breaking but not urgent.

@chlowell chlowell merged commit 5df8693 into Azure:main Jun 30, 2021
@chlowell chlowell deleted the regional branch June 30, 2021 00:54
rakshith91 pushed a commit to rakshith91/azure-sdk-for-python that referenced this pull request Jul 16, 2021
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-python that referenced this pull request Jun 22, 2022
[Hub Generated] Add missing listProducts API to documentation (Azure#19392)

* Add specification for list products

* Add spec to 2016-01-01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for Managed Identity regional AAD authentication endpoints
2 participants