depends_on usage in Python version

Hi,

CDKTF version: 0.11.2

I have got the need to specify that a resource depends_on on other. This is what I am trying to do:

created_schema = Schema(self,
                                    id_=schema["name"],
                                    database=schema["database"],
                                    name=schema["name"])

snowflake_table = SnowflakeTableModule(self,
                                               id_=f"{schema}_{table['name']}",
                                               columns=table_columns,
                                               database_name=database,
                                               schema_name=schema,
                                               table_name=table["name"],
                                               change_tracking=table["change_tracking"],
                                               data_retention_days=table["data_retention_days"])

 snowflake_table.add_override("depends_on", [Token.as_any(created_schema.fqn)])

It does not create errors during synth and indeed I see the following in the generated json:

"depends_on": [
        "${snowflake_schema.snowflake_schemas_DEMO2_BAZAARVOICE_STANDARD_CLIENT_FEED_07181D8A}"
      ],

But then, when trying to run terraform plan, I get:

│ Error: Invalid expression
│ 
│   on cdk.tf.json line 37, in module.snowflake_schemas_test_table_1_044C1F2F.depends_on:
│   37:         "${snowflake_schema.snowflake_schemas_test_07181D8A}"
│ 
│ A single static variable reference is required: only attribute access and
│ indexing with constant keys. No calculations, function calls, template
│ expressions, etc are allowed here.

Anyone knows how to fix this?

[hragarwal]

@jsteinich this is custom module but weirdly it doesn’t have depends_on in the constructor parameters when module bindings are generated, anything specific needs to be done to add it in constructor while generation or creation of module ?

[github-actions[bot]]

I’m going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you’ve found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.