Skip to content
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

Errors when destroying Service Principal Passwords - azuread #599

Closed
pjoe opened this issue Jun 11, 2020 · 2 comments
Closed

Errors when destroying Service Principal Passwords - azuread #599

pjoe opened this issue Jun 11, 2020 · 2 comments
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed

Comments

@pjoe
Copy link

pjoe commented Jun 11, 2020

Seeing weird errors when destroying Service Principal Password:

Diagnostics:
  azuread:index:ServicePrincipalPassword (k8s-dev-SpPassword-ExtDNS):
    error: deleting urn:pulumi:k8s::tms-pulumi::azuread:index/servicePrincipalPassword:ServicePrincipalPassword::k8s-dev-SpPassword-ExtDNS: Error parsing Application Password ID: Credential ID should be in 
the format {objectId}/{keyType}/{keyId} - but got "f0aad1c4-****-4629-929e-b4f2da41****/33ee0852-****-****-17d0-33b52a02****"

This happened with:

  • pulumi: 2.4.0
  • pulumi/azure: 3.8.0
  • pulumi/azuread: 2.3.0

I tried downgrading a couple of versions but got same error.

In the end I had to export the stack, remove in the json and then import.

I have earlier successfully destroyed stacks with SpPasswords, so guessing something must have changed.

@mikhailshilkov
Copy link
Member

It sounds like a consequence of hashicorp/terraform-provider-azuread#264

Does it work if you create this resource again with the newest version, and then delete it?

@mikhailshilkov mikhailshilkov added kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed labels Aug 7, 2023
@mikhailshilkov
Copy link
Member

As mentioned above, I assume the problem was caused by a breaking change between two old versions. Since no comments were posted since 2020, I'll go ahead and close the issue as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

No branches or pull requests

2 participants