Sebastian
Sebastian
just came across the same issue. This really need to be solved. How else do you propose people can be sure config changes are applied?
> In order to support connecting to Key Vault over a Private Endpoint, we'd need to switch to using the Resource Manager API to do this, which may include permission...
@gabrielmccoll we solved a similar situation when using Private Build Agents with Key Vault and Private Endpoints by the use of a deployment timer: ``` resource "azurerm_key_vault" "stamp" { name...
make sure the key vault gets newly deployed. The timer only applies the first time when the KV is actually getting created. On the next runs the timer should not...
looks like somewhere in your TF state you still have references to some KV-child resources (certificates?!). TF tries to check their state I guess. Try to start from a completely...
I'm totally fine if the behavior is right now that it produces a tar file instead of a gzip. But then the docs must not refer everywhere to it with...
Yeah I came across it in the announcment blog - which links to the issue #283 as well as the PR, both say "tar.gz" https://github.com/dotnet/sdk/pull/35151
> Excellent catch folks - I think it's best to try and fix doc mentions of tar.gz in the docs first, then add explicit support for toggling compression as a...