This repository was archived by the owner on Jan 21, 2025. It is now read-only.
[cadl-ranch-*] Backport the server testing changes from typespec repository to cadl-ranch repository #741
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 1494b41 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
packages/cadl-ranch-specs/http/authentication/http/custom/mockapi.ts
Dismissed
Show dismissed
Hide dismissed
packages/cadl-ranch-specs/http/authentication/http/custom/mockapi.ts
Dismissed
Show dismissed
Hide dismissed
packages/cadl-ranch-specs/http/authentication/oauth2/mockapi.ts
Dismissed
Show dismissed
Hide dismissed
packages/cadl-ranch-specs/http/authentication/union/mockapi.ts
Dismissed
Show dismissed
Hide dismissed
sarangan12
commented
Oct 4, 2024
packages/cadl-ranch-specs/http/azure/resource-manager/models/resources/mockapi.ts
Show resolved
Hide resolved
sarangan12
commented
Oct 4, 2024
sarangan12
commented
Oct 4, 2024
sarangan12
changed the title
sarangan12
requested review from
iscai-msft,
lmazuel,
m-nash,
joheredi,
srnagar,
weidongxu-microsoft,
tadelesh and
timotheeguerin
as code owners
XiaofeiCao
approved these changes
Oct 8, 2024
github-merge-queue bot
pushed a commit
to microsoft/typespec
that referenced
this pull request
Oct 9, 2024
) 1. As part of cadl-ranch migration, several packages have been migrated from cadl-ranch repository to typespec repository. Once the split is complete during the development, there were some changes that were pushed in cadl-ranch repository. Those changes must be shifted back to typespec repository. 2. Also, few changes are required in the packages to handle the azure specific specs (These changes are added as part of the PR: Azure/cadl-ranch#741). 3. In addition, I have created a new package called `@azure-tools/azure-http-specs` has been created in the `typespec-azure` repository. This package has only the azure specific specs. I have tested the changes including the `pnpm test:e2e`. All validations are successful. The changes in this PR will be required for creating the PR for `@azure-tools/azure-http-specs` (which I will create once this PR is merged). Please review and approve this PR. Thanks
for a short period of time if you need to update teh typespec scenarios you should update it in both place. For azure we are also moving them to the typespec-azure repo so you will need to update it there when that is done too. When that is done we'll try to quickly rollout on having everyone use the new typespec and typespec-azure version instead so we can stop maintaining this repo |
iscai-msft
approved these changes
Oct 10, 2024
github-merge-queue bot
pushed a commit
to Azure/typespec-azure
that referenced
this pull request
Oct 11, 2024
…st Typespec (#1665) This is a spin-off of PR Azure/cadl-ranch#741. A new package `@azure-tools/azure-http-specs` has been created to handle only the azure specific scenarios and the scenarios that are not included in the `@typespec/http-specs` package. Please review and approve the PR. Note: 1. The `test:e2e` script is working fine. 2. I have not deleted the `cadl-ranch-specs` folder under `e2e-tests` folder and not modified the `e2e-tests.mjs` script.
tadelesh
added a commit
that referenced
this pull request
Oct 11, 2024
tadelesh
added a commit
that referenced
this pull request
Oct 11, 2024
iscai-msft
pushed a commit
to Azure/typespec-azure
that referenced
this pull request
Oct 16, 2024
…st Typespec (#1665) This is a spin-off of PR Azure/cadl-ranch#741. A new package `@azure-tools/azure-http-specs` has been created to handle only the azure specific scenarios and the scenarios that are not included in the `@typespec/http-specs` package. Please review and approve the PR. Note: 1. The `test:e2e` script is working fine. 2. I have not deleted the `cadl-ranch-specs` folder under `e2e-tests` folder and not modified the `e2e-tests.mjs` script.
swatkatz
pushed a commit
to swatkatz/typespec
that referenced
this pull request
Nov 5, 2024
…crosoft#4637) 1. As part of cadl-ranch migration, several packages have been migrated from cadl-ranch repository to typespec repository. Once the split is complete during the development, there were some changes that were pushed in cadl-ranch repository. Those changes must be shifted back to typespec repository. 2. Also, few changes are required in the packages to handle the azure specific specs (These changes are added as part of the PR: Azure/cadl-ranch#741). 3. In addition, I have created a new package called `@azure-tools/azure-http-specs` has been created in the `typespec-azure` repository. This package has only the azure specific specs. I have tested the changes including the `pnpm test:e2e`. All validations are successful. The changes in this PR will be required for creating the PR for `@azure-tools/azure-http-specs` (which I will create once this PR is merged). Please review and approve this PR. Thanks
markcowl
pushed a commit
to markcowl/typespec-azure
that referenced
this pull request
Dec 5, 2024
…st Typespec (Azure#1665) This is a spin-off of PR Azure/cadl-ranch#741. A new package `@azure-tools/azure-http-specs` has been created to handle only the azure specific scenarios and the scenarios that are not included in the `@typespec/http-specs` package. Please review and approve the PR. Note: 1. The `test:e2e` script is working fine. 2. I have not deleted the `cadl-ranch-specs` folder under `e2e-tests` folder and not modified the `e2e-tests.mjs` script.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of
cadl-ranchmigration, several packages have been migrated fromcadl-ranchrepository totypespecrepository. Now, the changes made to thetypespecrepository has to be backported to thecadl-ranchrepository. This PR accomplishes that.This PR consists of the following changes:
cadl-ranch-api&cadl-ranchpackages have been migrated from the corresponding packages in thetypespecrepository. Except for 3 design changes, there is no bigger changes. These 3 changes are indicated in the PR Comments.cadl-ranch-specsrepository have been migrated from the corresponding package in thetypespecrepository. In addition to the endpoints in thetypespecrepository, the following folders have been migrated to new model:This change is done for 2 reasons. One, We do not want anyone to add new features in these folders using the old model. Second, I am planning to port these folders to the new package
azure-http-specsfor which I will create the PR shortly after this is merged.I have already executed e2e scenarios and all validations are successful.
Note I have not made any major/minor version bumps for any of the 3 packages involved in this PR
Please review and approve the PR. Thanks