microsoft / microsoft/powerbi-powershell
Dataflow Management Support
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 413
- Forks
- 134
- Avg merge
- 33m
- Merged PRs (30d)
- 1
Description
We are currently working to setup GitHub actions for Data flow deployments. We use SPNs but Dataflows management is not supported using SPN.
https://docs.microsoft.com/en-us/power-bi/developer/embedded/embed-service-principal#considerations-and-limitations
While we invoke the following:
Invoke-PowerBIRestMethod -Url $url -Method Post -Body $body | ConvertFrom-Json
we get:
Invoke-PowerBIRestMethod: /Users/*********:
Line |
88 | … loyResult = Invoke-PowerBIRestMethod -Url $url -Method Post -Body $b …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| One or more errors occurred. (Response status code does not indicate success: 400 (Bad Request).)
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 documented Power BI service-principal limitations and the reported Invoke-PowerBIRestMethod call in the issue. Reproduce the 400 response for the dataflow deployment request, then determine the scope needed for dataflow management with SPNs; done means the supported deployment path works without that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, powershell
- Domain
- api, cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100