Toro

My setup: ``` Packer -> HAproxy (tcp) -> Caddy (http) -> vCenter API ``` The odd thing was that I errored out at the ~1min mark... ``` 2020/01/11 06:18:50 [INFO]...

I had this error: ``` vsphere-iso: error typing a boot command: ServerFaultCode: Permission to perform this operation was denied. ``` Tested with: Packer 1.3.4 vSphere-iso 2.3 ESXi 6.7 U3 vCenter...

Success, this is what I was able to do: ``` root@ClearLinuxWLG ~ # parted -a none /dev/sda ---pretend-input-tty resizepart 3 Yes 64420MB Warning: Partition /dev/sda3 is being used. Are you...

Having the same issue with Node and Powershell functions.

> A very frequent use case is so that it is possible to preserve the source IP address through the proxy protocol as delivered by the cloud load balancers. ie...

Encountered the same issue with `1.15.0-rc.0`. I was able to workaround it by following @cornfeedhobo nginx hack #29985. After getting around that I got recurring 'reconnecting' error messages popping up...

any chance we can have something while the ideal solution is worked on? this kinda ruins the tidyness of using the YAML source option.

Still happening in 2024 🤣 What makes this even worse is the BS AI answers from Pulumi where it just makes stuff up:  https://www.pulumi.com/ai/answers/c7CeZ6aZNNFmFPUc3SVzQy/registering-azure-resource-providers-for-successful-deployments.

So if because of this one has to use the Terraform provider, we also need to set ARM_SKIP_PROVIDER_REGISTRATION right? Unless we use the Terraform provider for additional resource creation, not...

> As a consequence, when your create a SMTP provider via terraform, it will recreate a new SMTP provider with the same configuration as long as one gets activated with...