pulumi up fails second time when using firestore Index

A index for firestore can easily be created by using:

    const backupIndex = new gcp.firestore.Index(
      "index",
      {
        collection: "mycollection",
        fields: [
          {
            fieldPath: "onefield",
            order: "ASCENDING",
          },
          {
            fieldPath: "anotherfield",
            order: "DESCENDING",
          },
        ],
      },
      {
        parent: this,
      }
    );

creates the index the first time pulumi up is executed. The second time however, even though no changes have been performed, a replace is scheduled for changing the fields:

 gcp:firestore:Index                                  index                replace     [diff: ~fields]

Furthermore this fails:

gcp:firestore:Index (backup):
    error: Error creating Index: googleapi: Error 409: index already exists

Ok, so lets try changing the name of the index:

+  gcp:firestore:Index                                  newIndex           create
- gcp:firestore:Index                                  index                delete

It also fails:

error: Error creating Index: googleapi: Error 409: index already exists

[leezen]

This is tracked in https://github.com/pulumi/pulumi/issues/2625

Regarding the diff you saw, could you please provide the detailed diff? I wonder if it’s an ordering thing with the API returning a different order, in which case, could this be solved by ordering the fields in the same order?

[manast]

regarding deleteBeforeReplace, I agree on what you say.