Implement more purview commands
Open
Nobody has claimed this yet.
epic
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 413
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 21
Description
Now that we are working on retention labels it also seems interesting to look at information protection and implement these commands:
- #4423
- #4424
- #4425
- #4426
- #4427
- #4428
- #4714
- #4715
- #4716
- #4717
- #5035
More info
- More info about sensitivity labels
- More info about sensitivity label policy
- More info about threat assessment
These apis for sensitivity labels & sensitivity label policy are currently only available in beta, so these should contain a remark in the documentation
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.
Research direction
Start with the remaining linked issues #4714 and #4715, then read the referenced sensitivity-label, policy-setting, and threat-assessment API documentation. Done means implementing the outstanding Purview commands and documenting that sensitivity-label APIs are beta.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100