Daniel Schaaff

I always get the response in this order ``` { "name": "test", "deploy_access_levels": [ { "access_level": 40, "access_level_description": "SRE", "user_id": null, "group_id": 51509863, "group_inheritance_type": 0 }, { "access_level": 40, "access_level_description":...

Curious about this as well. I'm unable to get a nodeSelector working with sharded thanos store. I'm not super familiar with jsonnet either. Following the example here https://github.com/thanos-io/kube-thanos/issues/181#issuecomment-786558196 gives me...

I figured this out FYI ``` local storeShardCount = 9; local strs = t.storeShards(commonConfig.config { replicas: 2, shards: storeShardCount, serviceMonitor: true, resources: { requests: { cpu: '6000m', memory: '18G', },...

I am experiencing this when ``` experiments { manifest = true } ``` is set in the provider config. If I remove the experiments config the provider works as expected.

This issue is still present in 1.9.3.

@shake76 I'll have test that out to confirm. I only verified that the builtin multi-line parser is not working in 1.9.3.

The big 1.0 rewrite has been released for a bit. Can anyone from HashiCorp comment on the timeline for fixing this issue? Due to the delay on this and [other...

We abandoned the Consul mesh after 2 years in production. We had to run a forked build of the controller to enable adding the pre stop sleep that entire time....

I'm experiencing the same thing, but haven't been able to look into the code yet to see if I can identify why.

This plugin has since added autocomplete and doesn’t have this behavior FYI https://marketplace.visualstudio.com/items?itemName=mauve.terraform