generated from ministryofjustice/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding PowerBI User permission set and policy #6120
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
julialawrence
had a problem deploying
to
production
February 2, 2024 11:32 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 11:32 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 11:32 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 11:32 — with
GitHub Actions
Failure
|
julialawrence
had a problem deploying
to
production
February 2, 2024 11:36 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 11:36 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 11:36 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 11:36 — with
GitHub Actions
Failure
|
julialawrence
had a problem deploying
to
production
February 2, 2024 11:53 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 11:53 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 11:53 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 11:53 — with
GitHub Actions
Failure
|
julialawrence
had a problem deploying
to
production
February 2, 2024 12:12 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 12:12 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 12:12 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 12:12 — with
GitHub Actions
Failure
|
julialawrence
had a problem deploying
to
production
February 2, 2024 12:51 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 12:51 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 12:51 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 12:51 — with
GitHub Actions
Failure
|
julialawrence
had a problem deploying
to
production
February 2, 2024 13:04 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 13:04 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 13:04 — with
GitHub Actions
Failure
|
julialawrence
force-pushed
the
feature/powerbi-author-permission-set
branch
from
February 2, 2024 13:09
d6e97b8
to
00d696e
Compare
julialawrence
had a problem deploying
to
production
February 2, 2024 13:09 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 13:09 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 13:09 — with
GitHub Actions
Failure
julialawrence
had a problem deploying
to
production
February 2, 2024 13:09 — with
GitHub Actions
Failure
|
julialawrence
had a problem deploying
to
production
February 2, 2024 13:22 — with
GitHub Actions
Failure
julialawrence
temporarily deployed
to
production
February 2, 2024 13:22 — with
GitHub Actions
Inactive
julialawrence
temporarily deployed
to
production
February 2, 2024 13:22 — with
GitHub Actions
Inactive
julialawrence
temporarily deployed
to
production
February 2, 2024 13:22 — with
GitHub Actions
Inactive
|
julialawrence
temporarily deployed
to
production
February 2, 2024 13:31 — with
GitHub Actions
Inactive
julialawrence
temporarily deployed
to
production
February 2, 2024 13:31 — with
GitHub Actions
Inactive
julialawrence
temporarily deployed
to
production
February 2, 2024 13:31 — with
GitHub Actions
Inactive
julialawrence
temporarily deployed
to
production
February 2, 2024 13:31 — with
GitHub Actions
Inactive
|
ASTRobinson
approved these changes
Feb 2, 2024
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A reference to the issue / Description of it
The purpose of this PR is to create an SSO permission set for use in a specific tactical business case - we are aware of the limitations here and this will not scale / is not expected to become an AP offering.
This is in reference to ministryofjustice/analytical-platform#2451 specifically.
The user modernisation-platform-powerbi-user shall be assumed by three analytical platform users to configure a data source made up of data being held in analytical platform, in order to make it available in the PowerBI service. This permission set is only to be used in the analytical-platform-data-production account.
This PR adds:
To do:
Add the permission set assignment in an AP account in a follow-up PR.
How does this PR fix the problem?
This creates a role for the users to assume that limits them to specific buckets to perform report generation.
How has this been tested?
The source policy for this is an existing user policy in the Analytical Platform account. The specific permissions testing is going to be carried out on 5/2
Deployment Plan / Instructions
The policy/permission set change is atomic. However, this adds another OPA test so it's important to make sure it's not causing unexpected OPA test failures for existing permission sets.
Checklist (check
x
in[ ]
of list items)