@neehhaa06 as a suggestion, I think Titan should have the following workflow. If warehouse exists, exclude initially_suspended parameter. That's point 1. Point number 2 is: why does it want to alter the existing warehouse when I didn't modify its resource definition in the first place? This seems like a bug to me.

@neehhaa06 what configuration can I check precisely? There are no logs to check for debugging purposes, as far as I can tell. And there is no configuration for the blueprint other than run_mode which is set to create-or-update.

This is my existing warehouse:

And these are the logs from the plan:

~ urn::XXX:warehouse/TITAN_TEST_WH {
  ~ query_acceleration_max_scale_factor = None -> 1
}

~ urn::XXX:warehouse/TITAN_TEST_WH {
  ~ scaling_policy = None -> "STANDARD"
}

~ urn::XXX:warehouse/TITAN_TEST_WH {
  ~ min_cluster_count = None -> 1
}

~ urn::XXX:warehouse/TITAN_TEST_WH {
  ~ max_cluster_count = None -> 1
}

However, if I also run SHOW PARAMETERS FOR WAREHOUSE TITAN_TEST_WH; we can only see:

which is probably not sufficient for Titan to know what the actual rest of the parameters of the warehouse are.

Fixed in v0.9.