-
Notifications
You must be signed in to change notification settings - Fork 15
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
Removing a deployed Data Safe Haven #2263
Comments
Looking at:
|
I think not - from the cli when I log into my entra.admin account
doesn't include any apps with pulimi in the name?
|
Can you double-check in the Entra portal (entra.microsoft.com) with the same admin account? It would be under |
DS Data Safe Haven (prod5) Pulumi Service Principal: 4ad821de-dcfc-477d-8bc0-bf00b5cf947f 22/10/2024 Current I think I might have deployed against the one which was deleted? |
Right - that might be true. Can you:
|
No - that's what I'm stuck on (I think)
Can try steps 2 and 3 through? |
Solution Find the .pulumi/stacks/data-safe-haven/shm-prod5-sre-srename.json and remove all blocks that reference/use "azuread" then GOTO the entra admin centre and delete the corresponding groups: "Data Safe Haven SRE |
Note this is because the Pulumi Service Principal was deleted and re-created between when this SRE was created and now. @JimMadge: is this something we should do better at warning about? Or, ideally, write something that can update the provider details? |
If I've understood correctly, my feeling is this is an edge case where ad-hoc changes to the TRE have created a state we can't account for. I'm not keen on trying to write code to account for things like this, it will add maintenance burden and be difficult to test/verify relative to how often it will be useful. I would rather add to the docs or add guard to stop this kind of thing happening (if the CLI caused this). |
✅ Checklist
💻 System information
📦 Packages
List of packages
🚫 Describe the problem
process fails when trying to tear down a SRE
Full error message
🚂 Workarounds or solutions
The text was updated successfully, but these errors were encountered: