Closed smithrobs closed 1 week ago
Thanks for reporting @smithrobs. I just tried to repro in TF and it wasn't able to:
terraform {
required_providers {
auth0 = {
source = "auth0/auth0"
version = ">= 1.0.0"
}
}
}
resource "auth0_connection" "my_connection_1" {
name = "My-Connection-1"
strategy = "auth0"
}
resource "auth0_connection" "my_connection_2" {
name = "My-Connection-2"
strategy = "auth0"
}
resource "auth0_organization" "my_organization" {
name = "auth0-inc"
display_name = "Auth0 Inc."
branding {
logo_url = "https://example.com/assets/icons/icon.png"
}
}
resource "auth0_organization_connections" "one_to_many" {
organization_id = auth0_organization.my_organization.id
enabled_connections {
connection_id = auth0_connection.my_connection_1.id
assign_membership_on_login = true
}
enabled_connections {
connection_id = auth0_connection.my_connection_2.id
assign_membership_on_login = true
}
}
Seems to either be a bug with the Pulumi provider or the bridge. Will investigate.
Tried reproducing with a stack created with v3.8.3 and the bug does not repro. Will attempt to repro with a stack created with v2, might be something related to state migrations.
This seems to be an issue with v2.24.3. The latest pulumi-auth0 (v3.8.3) is not affected.
Note that in order to use the latest version for the destroy you need to:
npm i
to install the packagepulumi up
with the newest version in order to change the provider for all resources. Without these steps the resources would still use the old 2.24.3 providerpulumi down
in order to delete the resources.@smithrobs can you please try that and report back if it works?
@VenelinMartinov Confirmed v3.8.3 does not panic after having the provider changed for real. Thank you!
Describe what happened
A
pulumi up
of the sample program succeeds. A subsequentpulumi destroy
fails with a panic.Happens with
@pulumi/auth0
v3.8.3 as well as v2.24.3Sample program
Log output
Affected Resource(s)
auth0.OrganizationConnections
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).