No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

would protecting the resource be sufficient? <https://www.pulumi.com/docs/intro/concepts/programming-model/#protect>

thanks <@UQ23ERNT1>, I will try this. But I though there was something like 'ignore_recreate' in ResourceOptions, which is available in terraform

# Changes to the value of `prop` will not lead to updates/replacements
res = MyResource("res", prop="new-value", opts=ResourceOptions(ignore_changes=["prop"]))

<@UHTP242EB>, fantastic, thanks a lot!
```opts=ResourceOptions(
                         depends_on=[cloud_pgsql_main_1],
                         ignore_changes=['name'],
                         protect=True,
                     ),```

They shouldn’t change if they are auto named...

<@UHTP242EB>, I will explain my use case. I want to create a GCP CloudSQL Postgres Database Instance and a Read Replica for it. Since GCP doesn't fully delete your database instance for a while, the name is reserved, so I've created a workaround like this:
```def random_string(string_length=5):
    """Generate a random string of fixed length """
    letters = string.ascii_lowercase
    return ''.join(random.choice(letters) for _ in range(string_length))```
to generate names for Database Instances in my test project, because I am experimenting with different settings and recreate instances very often. Then I utilise it:
```MASTER_INSTANCE_NAME = config.get('psql_instance_name') or get_project() +\
                '-psql-main-1-' + random_string()

cloud_pgsql_main_1 =\
    DatabaseInstance('cloud_pgsql_main_1',
                     opts=ResourceOptions(
                         depends_on=[sql_admin_api],
                         ignore_changes=['name'],
                         protect=True,
                     ),
                     database_version='POSTGRES_11',
                     name=MASTER_INSTANCE_NAME,```

Ah :) nice workaround eventual consistency

<@UHTP242EB> it seems like protect for python SDK is not working properly. When I set it to False it still says
```error: Preview failed: refusing to delete protected resource```

Did you run `pulumi up`  after setting it to false, before making a change that forces recreation?

yes, I think it also depends on
```ignore_changes=```
