microsoft / microsoft/powerbi-powershell
Pull gateway configuration and datasources
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 413
- Forks
- 134
- Avg merge
- 33m
- Merged PRs (30d)
- 1
Description
One major hurdle we have is an ability to central manage and monitor gateways tied to our org. while the latest subset of commandlets are a nice step in allowing org admins to view datasets, etc. still appears that security and management is taken a back seat to product. I was originally told that gateway management/monitoring was supposed to be released in Q2 of 2018 and here we are half way through Q3. I really want to release gateway to users however with the current subset of available powershell commands and auditing, I can not at this time. while the current gateway and powerbi empowers the users, it also fosters a mindset of shadow IT which is a bad thing in large IT enterprises. Gateways provide a proxy for users to share information, and without the ability to query what is shared or configured sensitive data could be inadvertently leaked to unauthorized individuals
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 existing PowerShell cmdlets and auditing capabilities for gateways, datasets, configuration, and datasources. Clarify the required management and monitoring scope with maintainers; done would require an agreed set of commands that can safely query and manage gateway configuration and shared datasources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- backend-api-design, cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100