Service already taken for customer / inputs to import do not match existing resource issue with Automation API

[HelloFillip]

Using Go and the Automation API I've been rolling up updates to a Fastly Compute service for months.

On a regular basis the process breaks with: Detail: Name 'Edge Compute Service' already taken for customer '...'. I've tried fixing this numerous ways, including re-examining my approach in #480. In the end, for time, I've torn down all of the services and re-run the process with a clean slate.

However, that's not practical and I'm trying to find a solution to this issue.

If I try and import the service and apply my changes (as described in #480), then I get: inputs to import do not match the existing resource: [backends loggingS3s package reuse]. However, every part of the service is in the same small piece of code: there has been no manual updates or updates outside of this process.

[t0yv0]

Have you tried https://www.pulumi.com/docs/iac/cli/commands/pulumi_import/ ?

[HelloFillip]

No. I'm using the Automotive API, rather than the terminal.

[t0yv0]

inputs to import do not match the existing resource: [backends loggingS3s package reuse] results from using the Resource import option. The intended flow is interactive of editing the inputs to match the imported inputs. There are some issues with this in the bridged providers (pulumi/pulumi-terraform-bridge#2272), however I cannot tell if this affects your use case.

I strongly suggest you use pulumi import instead of the import option. This is available in Automation API as well as CLI version of Pulumi (such as https://github.com/pulumi/pulumi/blob/1f21cf747e9b6f135a8b13c11bcb43a61b224bcc/sdk/go/auto/stack.go#L494)

If you believe there is a specific issue with the fastly provider, please provide a minimal repro we can look at. Appreciated.

[HelloFillip]

Thanks. I’ve used the import in the Automation API which is what’s resulting in that error.

Everything I’m building is going to be open sourced so I’ll find the smallest part and share.

My personal site is probably the simplest and has this issue.

Just to be clear before I dig it out, I’ve tried with import and without. Without results in the “… already taken by customer… “ error.

With import results in the inputs to import do not match the existing resource error.

I’ll get back to this in the next day once I have useful code.

[HelloFillip]

I've instead thrown together a quick repository for another project that does very little.

Since adding the ImportResource code as an experiment it's now trying to tear down the entire Fastly Compute service (and failing because the version is live).

The repository is here: https://gitlab.com/Omnijar/Bushido/kamakura/composer.

The code I've added is:

resourcesToImport := []*optimport.ImportResource{
	{
		Type: "fastly:index/serviceCompute:ServiceCompute",
		ID:   serviceId,
		Name: "Taira Edge Compute",
	},
}

It can be found here: https://gitlab.com/Omnijar/Bushido/kamakura/composer/-/blob/trunk/compute/stack.go?ref_type=heads.

The error is:

fastly:index:ServiceCompute (Taira Edge Compute):
    error:   sdk-v2/provider2.go:515: sdk.helper_schema: 400 - Bad Request:
    
        Title:  Bad request
        Detail: Cannot delete service with active version
        RateLimitRemaining: 989
        RateLimitReset:     1740661200: provider=fastly@8.14.0
    error: deleting urn:pulumi:production::kamakura-edge-compute::fastly:index/serviceCompute:ServiceCompute::Taira Edge Compute: 1 error occurred:
        * 400 - Bad Request:
    
        Title:  Bad request
        Detail: Cannot delete service with active version
        RateLimitRemaining: 989
        RateLimitReset:     1740661200

This service did not exist until I wrote this code and executed it in the past hour. I then added the ImportResource code and re-ran the program resulting in the above error.

I am assuming at this point that the new issue is related to a lack of understanding on how to apply the import into an update, so I'm good with a pointer into my mistake, and once I rectify it I can re-attempt to reproduce it. This code is a very small subset of the original code and will make a useful example to validate whether this issue is real or a result of developer error.