feat: block oas until a4d is activated #6046
Open
+33
−6
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
mingxuanzhangsfdx
changed the title
peternhale
requested changes
Jan 30, 2025
peternhale
approved these changes
Jan 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Registered 2 commands to be executed by a4d when it is fully activated or deactivated. When the activating command runs, the OAS commands will be enabled to customers;
When the deactivating command runs, the OAS commands will be disabled to customers.
What issues does this PR fix or reference?
@W-17704904@
Functionality Before
OAS commands is forever exposed to customers even if a4d is missing.
Functionality After
OAS commands is blocked until a4d is activated, and is blocked after a4d is deactivated