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

Update configs to use new TME tenant #37667

Merged
merged 1 commit into from
Oct 7, 2024

Conversation

weshaggard
Copy link
Member

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

@weshaggard
Copy link
Member Author

/azp run python - documentintelligence - tests

Copy link

Azure Pipelines failed to run 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run python - documentintelligence - tests

Copy link

Azure Pipelines failed to run 1 pipeline(s).

@weshaggard weshaggard force-pushed the AddTMECloudConfig branch 2 times, most recently from 849e5f1 to 3fe7801 Compare October 1, 2024 17:53
@weshaggard
Copy link
Member Author

/azp run python - keyvault - tests

Copy link

Azure Pipelines failed to run 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run python - documentintelligence - tests

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard weshaggard force-pushed the AddTMECloudConfig branch 2 times, most recently from b41b4fa to 4cc1d9f Compare October 1, 2024 18:18
@weshaggard
Copy link
Member Author

/azp run python - keyvault - tests

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run python - documentintelligence - tests

Copy link

Azure Pipelines failed to run 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run python - documentintelligence - tests

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run python - keyvault - tests

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run python - documentintelligence - tests

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run python - documentintelligence - tests

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run python - documentintelligence - tests

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run python - keyvault - tests

@weshaggard weshaggard requested a review from scottaddie October 2, 2024 23:01
@weshaggard
Copy link
Member Author

/azp run python - monitor - tests

@weshaggard
Copy link
Member Author

/azp run python - identity - tests-weekly

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

1 similar comment
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run python - storage - tests

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run python - search - tests

@weshaggard
Copy link
Member Author

/azp run python - storage - tests

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

1 similar comment
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run python - servicebus - tests-weekly

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run python - keyvault - tests-weekly

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@@ -8,6 +8,7 @@ extends:
Clouds: Public_FarmBeats
CloudConfig:
Public_Farmbeats:
ServiceConnection: azure-sdk-tests-public #Might need a specific service connection if this is a unique sub.
Copy link
Member

Choose a reason for hiding this comment

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

@weshaggard I checked and they are using a custom sub (5bae917c-5fc9-40c5-923d-adbd52759048). I don't have access though.

Copy link
Member Author

Choose a reason for hiding this comment

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

I don't think they care much about this pipeline currently as the existing client secret is also not working. So, either way they will need to spend time to fix this when they are interested.

Copy link
Member

Choose a reason for hiding this comment

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

@weshaggard what is the guidance for services that use a custom sub? Our openai tests use static resources from a non-SDK team owned sub.

Copy link
Member

Choose a reason for hiding this comment

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

There is no general guidance. We need to look into them case by case.

Copy link
Member

@benbp benbp left a comment

Choose a reason for hiding this comment

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

+1 with the farmbeats caveat

- Update usgov and china configs to use default service connection
@weshaggard
Copy link
Member Author

@xiangyan99 @scbedd could you please review this PR? I'm not planning on blocking on all the test failures but I believe I have the test deployments working and individual teams will need to look at the test pipelines for failures. There may be some work needed enable things in the new TME sub but individual teams will need to work on that.

Copy link
Member

@scbedd scbedd left a comment

Choose a reason for hiding this comment

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

Approved. Ignore farmbeats errors on merge.

Copy link
Member

@pvaneck pvaneck left a comment

Choose a reason for hiding this comment

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

LGTM - Monitor test pipeline failure is due to an unrelated issue.

@weshaggard weshaggard merged commit c759481 into Azure:main Oct 7, 2024
333 of 346 checks passed
@weshaggard weshaggard deleted the AddTMECloudConfig branch October 7, 2024 23:27
@mccoyp mccoyp mentioned this pull request Oct 14, 2024
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.

8 participants