[Question] version set apiops , deploement from dev to qa enviroment
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
No files, tests, or entry points are named. Start by reviewing the APIOps version-set export and dev-to-QA deployment workflow, then compare the generated branch structure with the expected two APIs within one version set; done when the repository behavior is confirmed and the issue has a documented resolution.
Written by the indexing model from the issue text.
Description
Release version
APIM v1.0.0
Question Details
i have one version set in which there is 2 version of API so when i run the APIOPS of that version i am having two different api on the branch but ideally it should be two api inside version set . my question is during the deployement from the dev to qa will it create the two different api or the 2 api inside the same version set ??
Expected behavior
there should be two api inside the version set in the branch after running the APIOPS
Actual behavior
there are two different api in the branch after running the APIOPS
Reproduction Steps
NA
- Dominant language
- C#
- Stars
- 448
- Forks
- 247
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/apiops
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
priority-0
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
StackExchange/StackExchange.Redis#3249 ·
-
[Feat] 조합 영역 구분선 개선 Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100