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

Added pipeline to validate spec location #33919

Merged
merged 1 commit into from
Jan 19, 2024

Conversation

raych1
Copy link
Member

@raych1 raych1 commented Jan 19, 2024

Purpose of this PR

The purpose is to gate on the REST API specifications used to release SDK are from the main branch of Azure/azure-rest-api-spec.

Packages impacted by this PR

All the data plane GA packages to be released.

I scanned through this python repo and identified 3 data plane services that have released GA packages but their configuration file either tsp-location.yaml or swagger\README.md reference the REST API specs from a non-main branch of Azure spec repo.
Please refer to this spreadsheet to get the details of all the violated packages.

After this PR is merged, the next GA release for these packages will be blocked. They need to correct the spec path before releasing GA packages.

Describe the problem that is addressed by this PR

Added a pipeline from common template to release pipeline to validate the REST API specification location is from the main branch of Azure/azure-rest-api-spec.

This validation will be skipped if the package to be released is non-GA package.

Provide a list of related PRs

The common script and pipeline were merged by another PR.
Azure/azure-sdk-tools#7451

FYI - The same change has been added to other language repos' release pipelines.
Azure/azure-sdk-for-net#40783
Azure/azure-sdk-for-java#38332
Azure/azure-sdk-for-js#28303

@lmazuel lmazuel merged commit 75d6c26 into main Jan 19, 2024
19 checks passed
@lmazuel lmazuel deleted the user/raych1/pipeline-validate-spec-location branch January 19, 2024 21:20
sofiar-msft pushed a commit to sofiar-msft/azure-sdk-for-python that referenced this pull request Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants