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

Sync eng/common directory with azure-sdk-tools for PR 2585 #16876

Merged
merged 6 commits into from
Jan 21, 2022

Conversation

azure-sdk
Copy link
Collaborator

Sync eng/common directory with azure-sdk-tools for PR Azure/azure-sdk-tools#2585 See eng/common workflow

@azure-sdk azure-sdk requested a review from scbedd January 21, 2022 00:14
@azure-sdk azure-sdk added Central-EngSys This issue is owned by the Engineering System team. EngSys This issue is impacting the engineering system. labels Jan 21, 2022
@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, please perform following steps:

For track 2 SDKs 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 go - [service] - ci

@scbedd scbedd merged commit 2483b3b into main Jan 21, 2022
@scbedd scbedd deleted the sync-eng/common-feature/breaking-change-sync-2585 branch January 21, 2022 20:57
seankane-msft added a commit that referenced this pull request Jan 28, 2022
* generated code for azcerts

* add readme and doc.go files

* formatting, added BeginCreateCertificate, although not a poller yet

* starting GetCertificate

* adding GetCertificate endpoint

* changed to a poller using GetCertificate, should be with GetCertificateOperation

* adding GetCertificateOperation

* added several more methods

* adding list certs method

* ListCertificates implementation, but test is not working yet

* adding CreateIssuer method

* adding GetIssuer

* adding issuer pager

* adding delete issuer method

* doc updates and UpdateIssuer method

* Adding contacts crud operations

* adding Get and Update CertificatePolicy

* adding UpdateCertificateProperties

* Added BeginRecoverDeletedCert method

* restore certificate backup

* removing the poller.go file

* adding list deleted certs func

* last test

* adding certificates to eng/config.json

* removing generated from two public models

* adding ci.yml file

* trigger ci run

* adding license file, format header, and running go fmt

* adding examples and readme

* adding delete and cancel operation funcs

* error handling on examples

* updating broken link

* adding a changelog

* changing Tags to map[string]string

* updating comments, pagers

* formatting

* Only fetch provision application oid via API if not supplied (#16878)

Co-authored-by: Ben Broderick Phillips <[email protected]>

* More resilient updating of ExpiringResource (#16789)

* Sync eng/common directory with azure-sdk-tools for PR 2585 (#16876)

* updating to target test-proxy that only gets filename from body of /start request

* update recording.go to send x-recording-file in body of /start request

Co-authored-by: scbedd <[email protected]>

* Sync eng/common directory with azure-sdk-tools for PR 2596 (#16894)

- Fix bug in Add-ReleaseLease helper script
- Enable better local logging for handling token
- Enable strict mode to help catch issues like this in the future

* Sync eng/common directory with azure-sdk-tools for PR 2578 (#16895)

* excluding duplicated env:USER in image tag

* NIT

* removing default repo name

Co-authored-by: Albert Cheng <[email protected]>

* renaming

* Changes for AZURE_CLIENT_SEND_CERTIFICATE_CHAIN (#16851)

* add support for AZURE_CLIENT_SEND_CERTIFICATE_CHAIN

* Update CHANGELOG.md (#16903)

* Update CHANGELOG.md

* Update version

* Update version.go

* Increment version for internal releases (#16905)

Increment package version after release of internal

* Sync eng/common directory with azure-sdk-tools for PR 2581 (#16910)

* Generate token for aad app.

* Remove testing mode

* Update Generate-AddToken.ps1

* Update Generate-AddToken.ps1

* Generate token inside of opensource API call scripts

* Add resource

* Address feedback

* Update eng/common/scripts/Get-AADIdentityFromGithubUser.ps1

Co-authored-by: Ben Broderick Phillips <[email protected]>

* Update eng/common/scripts/Get-AADIdentityFromGithubUser.ps1

Co-authored-by: Ben Broderick Phillips <[email protected]>

* Remove the printout

* Update eng/common/scripts/Get-AADIdentityFromGithubUser.ps1

Co-authored-by: Wes Haggard <[email protected]>

* Update eng/common/scripts/Get-AADIdentityFromGithubUser.ps1

Co-authored-by: Ben Broderick Phillips <[email protected]>

* Added PS script strict mode

* Update Get-AADIdentityFromGithubUser.ps1

* Update Get-AADIdentityFromGithubUser.ps1

Co-authored-by: sima-zhu <[email protected]>
Co-authored-by: Sima Zhu <[email protected]>
Co-authored-by: Ben Broderick Phillips <[email protected]>
Co-authored-by: Wes Haggard <[email protected]>

* Syncing eng/common (#16904)

Co-authored-by: Albert Cheng <[email protected]>

* [Release] sdk/resourcemanager/storage/armstorage/0.4.0 generation from spec commit: d830271b241897bad300f9275ff7b27d502aa6c5 (#16913)

* [Tables] updating recordings for latest breaking change (#16906)

* updating recordings for latest breaking change

* go mod tidy

* reverting eng changes to docker tool instead of proxy direct

* running docker dump twice

* Update azidentity recordings (#16912)

* [KeyVault] Update recordings (#16917)

* updating azsecrets and azkeys

* updating azkeys recordings

* [azservicebus] Fixing several reliability/recovery bugs (#16831)

Fixing several reliability and recovery bugs that were affecting sending and receiving. This PR finally exports retry options so callers can configure how long and how many retries they want.

The big changes:
* Retry configuration options are now exposed through the ClientOptions for both the Admin client and the Service Bus client.
* amqpLinks.go has it's own Retry mechanism, based on the azcore retry algorithm. This does exponential backoff, jitter and is configurable using Client.RetryOptions. This retry mechanism cleans up several areas that were doing the BackoffRetrier before.
* MgmtClient is gone, and we just use rpcLink now. There were some coordination issues that just weren't working properly, so the rpc link code has been moved into azservicebus for now (it was always an internal type and remains so). 
* Sender/Receiver both use the better amqplinks.Retry() and their code has been structured to make that easier to read (hopefully!)

Bug fixes:
* Fixed a bug where the proper error wasn't being broadcast when the connection failed in rpc, preventing proper connection recovery.
* Fixed a bug where links wouldn't properly recreate if the connection recovery happened in the claim negotiation.

Fixes #15170 (Connection/network recovery)
Fixes #15610 (Error handling needs work to be consistent and reliable)
Fixes #15642 (Unify all the various retry mechanisms)

These were fixed by more or less sidestepping retryableRPC() mechanism:
Fixes #15644 (amqp-common's retryableRPC method returns string errors)
Fixes #16088 (amqp-common's link.RetryableRPC() retries an entity does not exist)

* fix incidentally added path addition (#16918)

Co-authored-by: scbedd <[email protected]>

* sdk generation pipeline script (#16782)

* compatible with old SDK generation and new codegen automation

* remove greedy suffix on link check (#16922)

Co-authored-by: Dane Walton <[email protected]>

* remove (#16919)

* Use Payload() for reading response bodies (#16911)

Poller.FinalResponse() wasn't restoring the response body after reading.
Removed duplicate definitions from GetJSON and bodyDownloadPolicy.

* [azservicebus] Explicitly reference gin-gonic until nhooyr.io/websocket is updated #16927

* return *Client

* removing LRO and pager interfaces

* all tests passing again

* updating and fixing a couple bugs, newest autorest version

* updating embedded models

* formatting

* updating to latest internal

* adding to doc.go

Co-authored-by: Azure SDK Bot <[email protected]>
Co-authored-by: Ben Broderick Phillips <[email protected]>
Co-authored-by: Charles Lowell <[email protected]>
Co-authored-by: scbedd <[email protected]>
Co-authored-by: Albert Cheng <[email protected]>
Co-authored-by: Christopher Scott <[email protected]>
Co-authored-by: sima-zhu <[email protected]>
Co-authored-by: Sima Zhu <[email protected]>
Co-authored-by: Ben Broderick Phillips <[email protected]>
Co-authored-by: Wes Haggard <[email protected]>
Co-authored-by: Jiahui Peng <[email protected]>
Co-authored-by: Richard Park <[email protected]>
Co-authored-by: chunyu3 <[email protected]>
Co-authored-by: Dane Walton <[email protected]>
Co-authored-by: Joel Hendrix <[email protected]>
benbp added a commit to benbp/azure-sdk-for-go that referenced this pull request Jan 28, 2022
* generated code for azcerts

* add readme and doc.go files

* formatting, added BeginCreateCertificate, although not a poller yet

* starting GetCertificate

* adding GetCertificate endpoint

* changed to a poller using GetCertificate, should be with GetCertificateOperation

* adding GetCertificateOperation

* added several more methods

* adding list certs method

* ListCertificates implementation, but test is not working yet

* adding CreateIssuer method

* adding GetIssuer

* adding issuer pager

* adding delete issuer method

* doc updates and UpdateIssuer method

* Adding contacts crud operations

* adding Get and Update CertificatePolicy

* adding UpdateCertificateProperties

* Added BeginRecoverDeletedCert method

* restore certificate backup

* removing the poller.go file

* adding list deleted certs func

* last test

* adding certificates to eng/config.json

* removing generated from two public models

* adding ci.yml file

* trigger ci run

* adding license file, format header, and running go fmt

* adding examples and readme

* adding delete and cancel operation funcs

* error handling on examples

* updating broken link

* adding a changelog

* changing Tags to map[string]string

* updating comments, pagers

* formatting

* Only fetch provision application oid via API if not supplied (Azure#16878)

Co-authored-by: Ben Broderick Phillips <[email protected]>

* More resilient updating of ExpiringResource (Azure#16789)

* Sync eng/common directory with azure-sdk-tools for PR 2585 (Azure#16876)

* updating to target test-proxy that only gets filename from body of /start request

* update recording.go to send x-recording-file in body of /start request

Co-authored-by: scbedd <[email protected]>

* Sync eng/common directory with azure-sdk-tools for PR 2596 (Azure#16894)

- Fix bug in Add-ReleaseLease helper script
- Enable better local logging for handling token
- Enable strict mode to help catch issues like this in the future

* Sync eng/common directory with azure-sdk-tools for PR 2578 (Azure#16895)

* excluding duplicated env:USER in image tag

* NIT

* removing default repo name

Co-authored-by: Albert Cheng <[email protected]>

* renaming

* Changes for AZURE_CLIENT_SEND_CERTIFICATE_CHAIN (Azure#16851)

* add support for AZURE_CLIENT_SEND_CERTIFICATE_CHAIN

* Update CHANGELOG.md (Azure#16903)

* Update CHANGELOG.md

* Update version

* Update version.go

* Increment version for internal releases (Azure#16905)

Increment package version after release of internal

* Sync eng/common directory with azure-sdk-tools for PR 2581 (Azure#16910)

* Generate token for aad app.

* Remove testing mode

* Update Generate-AddToken.ps1

* Update Generate-AddToken.ps1

* Generate token inside of opensource API call scripts

* Add resource

* Address feedback

* Update eng/common/scripts/Get-AADIdentityFromGithubUser.ps1

Co-authored-by: Ben Broderick Phillips <[email protected]>

* Update eng/common/scripts/Get-AADIdentityFromGithubUser.ps1

Co-authored-by: Ben Broderick Phillips <[email protected]>

* Remove the printout

* Update eng/common/scripts/Get-AADIdentityFromGithubUser.ps1

Co-authored-by: Wes Haggard <[email protected]>

* Update eng/common/scripts/Get-AADIdentityFromGithubUser.ps1

Co-authored-by: Ben Broderick Phillips <[email protected]>

* Added PS script strict mode

* Update Get-AADIdentityFromGithubUser.ps1

* Update Get-AADIdentityFromGithubUser.ps1

Co-authored-by: sima-zhu <[email protected]>
Co-authored-by: Sima Zhu <[email protected]>
Co-authored-by: Ben Broderick Phillips <[email protected]>
Co-authored-by: Wes Haggard <[email protected]>

* Syncing eng/common (Azure#16904)

Co-authored-by: Albert Cheng <[email protected]>

* [Release] sdk/resourcemanager/storage/armstorage/0.4.0 generation from spec commit: d830271b241897bad300f9275ff7b27d502aa6c5 (Azure#16913)

* [Tables] updating recordings for latest breaking change (Azure#16906)

* updating recordings for latest breaking change

* go mod tidy

* reverting eng changes to docker tool instead of proxy direct

* running docker dump twice

* Update azidentity recordings (Azure#16912)

* [KeyVault] Update recordings (Azure#16917)

* updating azsecrets and azkeys

* updating azkeys recordings

* [azservicebus] Fixing several reliability/recovery bugs (Azure#16831)

Fixing several reliability and recovery bugs that were affecting sending and receiving. This PR finally exports retry options so callers can configure how long and how many retries they want.

The big changes:
* Retry configuration options are now exposed through the ClientOptions for both the Admin client and the Service Bus client.
* amqpLinks.go has it's own Retry mechanism, based on the azcore retry algorithm. This does exponential backoff, jitter and is configurable using Client.RetryOptions. This retry mechanism cleans up several areas that were doing the BackoffRetrier before.
* MgmtClient is gone, and we just use rpcLink now. There were some coordination issues that just weren't working properly, so the rpc link code has been moved into azservicebus for now (it was always an internal type and remains so). 
* Sender/Receiver both use the better amqplinks.Retry() and their code has been structured to make that easier to read (hopefully!)

Bug fixes:
* Fixed a bug where the proper error wasn't being broadcast when the connection failed in rpc, preventing proper connection recovery.
* Fixed a bug where links wouldn't properly recreate if the connection recovery happened in the claim negotiation.

Fixes Azure#15170 (Connection/network recovery)
Fixes Azure#15610 (Error handling needs work to be consistent and reliable)
Fixes Azure#15642 (Unify all the various retry mechanisms)

These were fixed by more or less sidestepping retryableRPC() mechanism:
Fixes Azure#15644 (amqp-common's retryableRPC method returns string errors)
Fixes Azure#16088 (amqp-common's link.RetryableRPC() retries an entity does not exist)

* fix incidentally added path addition (Azure#16918)

Co-authored-by: scbedd <[email protected]>

* sdk generation pipeline script (Azure#16782)

* compatible with old SDK generation and new codegen automation

* remove greedy suffix on link check (Azure#16922)

Co-authored-by: Dane Walton <[email protected]>

* remove (Azure#16919)

* Use Payload() for reading response bodies (Azure#16911)

Poller.FinalResponse() wasn't restoring the response body after reading.
Removed duplicate definitions from GetJSON and bodyDownloadPolicy.

* [azservicebus] Explicitly reference gin-gonic until nhooyr.io/websocket is updated Azure#16927

* return *Client

* removing LRO and pager interfaces

* all tests passing again

* updating and fixing a couple bugs, newest autorest version

* updating embedded models

* formatting

* updating to latest internal

* adding to doc.go

Co-authored-by: Azure SDK Bot <[email protected]>
Co-authored-by: Ben Broderick Phillips <[email protected]>
Co-authored-by: Charles Lowell <[email protected]>
Co-authored-by: scbedd <[email protected]>
Co-authored-by: Albert Cheng <[email protected]>
Co-authored-by: Christopher Scott <[email protected]>
Co-authored-by: sima-zhu <[email protected]>
Co-authored-by: Sima Zhu <[email protected]>
Co-authored-by: Ben Broderick Phillips <[email protected]>
Co-authored-by: Wes Haggard <[email protected]>
Co-authored-by: Jiahui Peng <[email protected]>
Co-authored-by: Richard Park <[email protected]>
Co-authored-by: chunyu3 <[email protected]>
Co-authored-by: Dane Walton <[email protected]>
Co-authored-by: Joel Hendrix <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Central-EngSys This issue is owned by the Engineering System team. EngSys This issue is impacting the engineering system.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants