kphunter

> I would like to use `kpt fn run` inside CI/CD pipelines that run in a cluster... https://github.com/GoogleContainerTools/kpt/issues/2158 So as far as I can tell, a pipeline based on [Kaniko](https://github.com/GoogleContainerTools/kaniko)...

Looking at this quickly it seems a bit more complicated than it needs to be, which will make maintenance a headache. If sharing credentials between several services, what about pointing...

This still appears to be an issue with the current version. `main.tf`: ``` terraform { backend "http" { } required_providers { docker = { source = "kreuzwerker/docker" version = "~>...

After trying a couple of different things it seems like an interplay between `docker_image.name` and `docker_container.image`... If `docker_container.image` is not a string but set to `docker_image.name.latest`, the `terraform apply` produces...

Hi Alan, For sure... We use the fantastic feed2js tool to support announcements that are broadcast to a number of sites. One of our contracts is with the Canadian government,...

I'm also having the same error. I'm trying to translate https://github.com/haproxytechblog/ingress-controller-external-example from the vagrant demo into an on-premise centos-based setup, without success.

This "infinite diff" also appears to be an issue with `vault_identity_group_policies` and `vault_identity_group`, however the workaround fixes the problem. Vault 1.9.1 Terraform v1.1.7 on darwin_amd64 + provider registry.terraform.io/hashicorp/vault v2.24.0

In my case, the GitLab tags had been removed but the `Releases` still contained refs that conflicted. Removing these allowed `semantic-release` to run error-free.

> @ericschmar I believe what @kphunter is saying is he had to use the GitLab Releases API to delete the corresponding releases. But tagging him will help get an answer...

I've also run into this issue, and I think it's because the ordering of operations is difficult to ascertain. Do replacements get applied before/after a patch? For example, if I...