Karolis Pocius

Oddly, I can reproduce the issue with 4.27.0 and 4.26.0 and it started happening in the last few days even though we haven't updated the module or the provider.

When the instance is running, it applies correctly, but every consecutive plan results in error. Only tried with PG, not sure what's the behavior on other DBs.

> Still, having an issue with this even when setting `ATLANTIS_GH_APP_SLUG` Running Atlantis `v0.18.1` It is very confusing and counter intuitive, but if you app is called `My Atlantis`, it's...

We're just an early warning system for GitHub issues https://www.githubstatus.com/incidents/gq1x0j8bv67v

All of them are.

This has been fixed and rolled out in `13.0.0` -- the issue can be closed.

I understand the issue is on the API side and not much can be done until `location` is provided, just wanted to leave a note for the sake of completion,...

This is not a bug and in fact is [documented](https://www.runatlantis.io/docs/terraform-versions.html#via-atlantis-yaml): > Alternatively, one can use the terraform configuration block's `required_version` key to specify an _exact_ version Could be a feature...

Tested this on 0.27.1 with both parallel plan and apply turned off -- it still goes ahead an happily plans the changes.

To make it worse, the extension seems to ignore `"gitlens.plusFeatures.enabled": false` setting, which is super annoying. Downgrading to `v13.0.4` is a workaround, but then you lose some of the recent...