This repository was archived by the owner on Oct 11, 2024. It is now read-only.
[TT-10190] Add allow-unsafe-oas flag #122
Merged
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
|
Kudos, SonarCloud Quality Gate passed!
|
tbuchaillot
approved these changes
Oct 19, 2023
furkansenharputlu
added a commit
that referenced
this pull request
Oct 24, 2023
…int-usage [TT-10190] Add allow-unsafe-oas flag
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.
This PR adds
--allow-unsafe-oasflag toupdate,syncandpublishcommands so that if it is set, it will stop usingoasAPI update endpoint in the dashboard. It will use classic API update endpoints instead.