Introduces support for documenting minimal command permissions. #6342
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.
Here's the PR that introduces documenting minimal permissions for CLI commands.
How to run:
npm run start:commands
npm run start:mocks
npm run start:devproxy
npm run start:permissions
. This script updates the file generated in step 3 with minimal scopes for each command. Then, for our documentation, we'll need to combine the information from the different examples to present in our docs. In most cases the scopes will be the same for all examples but on an occasion that some examples require different scopes, we catch that too.The script will stop on the first error it encounters. This is intentional as we're still developing it, so that we can easily find and address errors.
When updating a command to support documenting its minimal permissions:
Also worth mentioning: this process right now only works with Graph-based commands. For other APIs, we'll need two things: