Open lluuiissoo opened 3 years ago
Looks good.
We could extend it like this:-
Scenario:
And an attempt to create a storage account "without" anonymous access "succeeds"
When the probr user is given appropriate RBAC role on the storage account
Then accessing the storage account anonymously fails
But accessing the storage account with the logged in probr user succeeds
Scenario Step | Implementation Plan |
---|---|
the probr user is given appropriate RBAC role on the storage account | Check if probr user has tbd RBAC role on the storage account (i.e. inherited from resource group). If not then add it to the storage account. This is more complicated that it sounds, so we should discuss how to do this. |
accessing the storage account anonymously fails | Try to LIST objects in the storage account without being logged into Azure |
accessing the storage account with the logged in probr user succeeds | Try to LIST objects in the storage account with the logged in probr user |
In terms of the RBAC step above, it's likely there are custom roles set up for storage accounts. So the probr user will need to
atScope()
filter it gives you all inherited roles on that objects
Please write a rough BDD specification [Replace sample below with actual BDD specification. See Gherkin syntax for reference: https://cucumber.io/docs/gherkin/reference]
Who is the SME validating this scenario? @iantivey