Add more support to unsupported SqlPermissions
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 460
- Forks
- 29
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 7
Description
- SqlPackage or DacFx Version:
- .NET Framework (Windows-only) or .NET Core:
- Environment (local platform and source/target platforms):
**Steps to Reproduce:**
1. We were able to remove the unsupported Sql permission statements from the deployment/import
2. We need to add these three cases
i. Revisit the permissions list and update SqlPlatform to any missing permission.
ii. Add a condition that checks object kind for the permissions, some similar permissions are shared between the objects but some are supported, and some are not.
iii. Add a user display message when we are not supporting that specific permission.
**Did this occur in prior versions? If not - which version(s) did it work in?**
(DacFx/SqlPackage/SSMS/Azure Data Studio)
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 by reviewing the SqlPlatform permissions list and the deployment/import handling described in the issue. Identify missing permissions, determine which object kinds support each shared permission, and define the user-facing message for unsupported permissions; done means all three cases are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- databases, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100