Bren

Try adding the `gavinbunney/kubectl` provider and running `terraform init -upgrade` Try your destroy again. ``` kubectl = { source = "gavinbunney/kubectl" version = ">= 1.14" } ``` ``` provider "kubectl"...

I was sure I had the same issue on destroy this am and through testing, copied the kubectl provider block from an eariler working setup and it fixed the issue....

No that was left in. Was also in my working example so left it in. Edit: I feel it's the `load_config_file = false` that's forcing terraform to renew it's short-lived...

Also looking at this, as I KNOW folks are going to ask for it. Even an eta would be great. Thanks guys.

I hit this issue (I think) today too. I imported the pagerduty_escalation_policy but I found I had to use the actual ID of the schedule vs say using `pagerduty_schedule.primary-schedule.id` ```...

More info on GitLab's Secure Partner Integration https://docs.gitlab.com/ee/development/integrations/secure_partner_integration.html

Stumbled across this issue today, least it appears to be the same issue I'm having. What info do you need to aid in a fix?

For me at least, it appears if I omit History -H the `configuration.xml` gets uploaded to the webserver just fine. The indexing appears to be fine.

> Per FluxCD: > > > The recommend way of installing Flux on Kubernetes clusters is by using the bootstrap procedure. > > Of which they list two methods -...

> Hi @propelup - we're actually introducing some new capabilities into the core NR UI that will allow us to replace the SLO/R app functionality. We're just in the midst...