[Bug] on_configuration_changes=apply does not add new index on incremental view

[LoicEm]

Is this a new bug?

• I believe this is a new bug
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

When I add a new index to an existing incremental model (see below), it is not created in the database

Expected Behavior

I would expect the new index to be created

Steps To Reproduce

1. This is the output of pip freeze | grep dbt

dbt-adapters==1.7.0
dbt-common==1.10.0
dbt-core==1.8.7
dbt-extractor==0.5.1
dbt-postgres==1.8.2
dbt-semantic-interfaces==0.5.1

3. Below is the original file test.sql I run

{{ config(
    materialized="incremental",
    on_configuration_changes="apply",
    indexes=[
        {'columns': ['a']}
             ]
    )
}}

select * from (VALUES(1, 'a'), (2, 'b'), (3, 'c')) as t(a, b)

dbt run --select test

4. Modify test.sql to add an index

{{ config(
    materialized="incremental",
    on_configuration_changes="apply",
    indexes=[
        {'columns': ['a']},
        {'columns': ['a', 'b']}
             ]
    )
}}

select * from (VALUES(1, 'a'), (2, 'b'), (3, 'c')) as t(a, b)

5. rerun dbt run --select test
6. A new index should be created (or the run should fail if on_configuration_changes="fail") but nothing happens.
7. Same behavior if I am removing the existing index, it is kept in place

Relevant log output

No response

Environment

- OS: Ubuntu 20.04
- Python:3.8.5
- dbt-postgres: 1.8.2

Additional Context

The related documentation on postgre website

[LoicEm]

My bad, it is clearly stated in the on_configuration_changes documentation that this currently only supported for materialized_view materialization.

I'm new to DBT, so I did not understand that this was a specific type of materialization at first, closing the issue