Seun Ore

@nfx Can we say that the migration of databricks namespace to `databricks/databricks` needs to done for `development`, `staging` and `production` environments at the same time, especially in situation where several...

@nfx , Just curious, do we need to be on terraform version `0.14+` for us to have successful migration of databricks provider namespace? I asked because currently in our configuration,...

> When following the update instructions, with a checked in .terraform.lock.hcl file, my plan is erroring and complaining about orphaned objects for users. Example: `Error: Provider configuration not present │...

> @barywhyte the share of provider adopters using tf v0.13, v0.12, and v0.11 is extremely low, hence I strongly recommend updating to the latest possible version. Approximately 80% of adopters...

All issues now resolved from my end. Had to apply `terraform state replace-provider databrickslabs/databricks databricks/databricks` command across my three deployment environments (dev, staging, prod) at the same time from a...

I am encountering same issue described by @prashanthbgoud. For users that use terraform to manage datadog monitors, I can only say that this migration link is at best nothing as...

> I would also like to be able to use env vars for example > ` SLACK_MESSAGE: ':x: App ${BRANCH} failed tests'` Unfortunately, this appear not to be supported. Basic...

@operatorequals That helped! Thank you! And thanks too for the correction about text alignment.

I am currently having this same issue but on Azure. Adding `nginx.ingress.kubernetes.io/whitelist-source-range: "74.234.138.x/32"` annotation basically make the service internally (from pods that have access within the same namespace) and externally...

I understand why this is so. Exporter for some reason was unable to establish connection to the DB instance. Spent hours trying to figure this out. Turns out that rebbot...