This repository has been archived by the owner on Feb 23, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 501
fix: Resolved operation schema does not exists error #872
Open
ratheeshps
wants to merge
1
commit into
Azure:main
Choose a base branch
from
ratheeshps:feature/fix-operation-schema-issue
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
fix: Resolved operation schema does not exists error #872
ratheeshps
wants to merge
1
commit into
Azure:main
from
ratheeshps:feature/fix-operation-schema-issue
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
@ratheeshps please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
ratheeshps
changed the title
Added to solve the operation reference schema does not exists error
Extractor: Added to solve the operation reference schema does not exists error
Jun 24, 2023
ratheeshps
changed the title
Extractor: Added to solve the operation reference schema does not exists error
Extractor: WIP - Added to solve the operation reference schema does not exists error
Jun 24, 2023
ratheeshps
changed the title
Extractor: WIP - Added to solve the operation reference schema does not exists error
Extractor: WIP - Resolved operation reference schema does not exists error
Jun 24, 2023
@microsoft-github-policy-service agree |
ratheeshps
changed the title
Extractor: WIP - Resolved operation reference schema does not exists error
Extractor: WIP - Resolved schema does not exists error
Jun 24, 2023
ratheeshps
changed the title
Extractor: WIP - Resolved schema does not exists error
Extractor: Resolved operation schema does not exists error
Jun 24, 2023
ratheeshps
changed the title
Extractor: Resolved operation schema does not exists error
fix: Resolved operation schema does not exists error
Jun 24, 2023
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.
Added to solve the operation reference schema does not exists error while deploying extracted ARMs from API Management Services.
While extracting if the QueryParameter linked to a schema, it is not adding dependsOn Microsoft.ApiManagement/service/apis/operations resource
See the error below.
##[error]At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.
##[error]Details:
##[error]ValidationError: Operation references schema that does not exist.