Jan Hudec

I would like to generalize this issue. `resource_group_name` getter (output) is missing in many resources. I've been mainly concerned about `containerservice.ManagedCluster`, `sql.Server` and `network.VirtualNetwork` as those I need to add...

I'm seeing the same symptoms with `destroy --target-dependents -t`, but destroying the dependents first worked, so it probably depends on what the resources are. In my case specifically the target...

After hitting it once more, this time with a plain recreate plan, I think the actual condition for triggering this is having a resource use a provider that depends on...

> Similar to #1917 Not similar, proposing a solution to. Regarding the solution, wouldn't it be better to provide the spec to the specific kubernetes_manifest resources themselves?

@DiamondLovesYou, would https://github.com/rust-lang/cargo/issues/1411 work for the tests?

> For anyone this may help, this is the extent of what I needed to add to the default "Node & TypeScript" `devcontainer.json` to get it running in rootless Podman:...

Shouldn't the `GetMutMany` trait be also `unsafe`? The `GetMutMany.get_mut_many` method is responsible for checking the places don't overlap, otherwise safety invariants are violated, so implementing the trait (because someone might...

@Hugzy, are you using the default kubernetes provider, or a customized one? Because what I was doing when I had the problem is that I read the parameters needed to...

I have even a bit worse problem: the server (and it's github serving releases) does not bother detecting or remembering the content type and simply says `application/octet-stream` even though the...

Workaround: Generate the `.env` file with `initCommand`.