Refactor how to create schemas without dropping schemas

[christoph-ding]

Hello, I have a question about how to change how schemas are defined by our provider.

Currently, we have 2 "sets" of schemas, and they are hardcoded in a local object (for the purposes of this example, we only care about the keys, which is the schema name, and not its values.
Let's call our sets A and B, and specific schemas have "schema" in their name:

locals {
  schemas = {
    A_schema_one,
    A_schema_two,
    A_schema_three,
    B_schema_one,
    B_schema_two,
    B_schema_three,
    ... etc
  }
}

We have decided this will scale poorly, and would like to shift to something programmatic:

locals {
  schemas = {
      schema_one,
      schema_two,
      schema_three,
      ... etc
  }
}

schema_names_set = toset(concat(
  keys(local.schemas),
  [for schema in keys(local.schemas) : "A_${schema}"],
  [for schema in keys(local.schemas) : "B_${schema}"],
  [for schema in keys(local.schemas) : "A_TEST_${schema}"],
  [for schema in keys(local.schemas) : "B_TEST_${schema}"],
))

The problem with this approach is that if we remove any schemas from the local list (for example, A_schema_one), it will destroy that schema, despite it being created programmatically later in the file.

I wanted to ask if anyone had a suggestion on how to proceed / solve this problem.