dennislapchenko

@denis256 @yorinasub17 @fgateuil GCS double impersonation is still big sore thumb :( can I assist you in writing tests to make this pass? Just couple pointers and I'll be happy...

Have a similar request, to be able to say: ``` locals { atlantis_workspace = "my_workspace" } ``` alongside a general `--create-workspaces`. This would allow joining some modules into one workspace...

> This looks great as a new flag, thanks for the contribution! By chance could you confirm if the tests pass locally for you? Yes, they do! somewhat inconvenient that...

@yorinasub17 Heya, followed your advice here to use `generate` instead of `remote_state`. Our bucket is created beforehand, so was no need. And we wouldnt even worry, until we started using...

@yorinasub17 thanks for the reply! I think a flag on `remote_state` would make the most sense. There is `skip_bucket_creation` and understanding to explicitly set it to `true` moved my investigation...

> Just add **message_thread_id** field to (https://prometheus.io/docs/alerting/latest/configuration/#telegram_config) why should it work if its undocumented? It doesnt seem like a field that would automatically work? :{

@udartsev it does not work as you suggested. alertmanager config: ``` telegram_configs: - send_resolved: false chat_id: -1001868435535 message_thread_id: 1486 ``` ``` image: prom/alertmanager:v0.26.0 ``` Error log: ``` ts=2023-11-08T14:53:42.575Z caller=coordinator.go:118 level=error...

Simply running generate and showing the result isnt sufficient for your usecases?