how to pass --dns to terraform-plan or terraform-apply?? #300
-
I need the ability to pass --dns options into docker run command that is effectively running the tf plan and apply. What is path of least resistance to do this? I have tried DOCKER_CONFIG env var, setting a custom json config to no avail. We are using twingate ZTN to talk to resources in azure privately including our tf plans and applies. This is also dependent on twingate pushing dns where the service principal isn't enough to access resources like storage that have networking restrictions active. We are using twingate headless linux client in another GHA step to pull dns for these specific resources. The docker run command rendered won't consistently respect DNS coming from twingate (on the github runner) unless we can somehow pass --dns options to the docker run. Please advise! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
I also tried hacking resolv.conf on the ubuntu-latest runner with no consistent results: |
Beta Was this translation helpful? Give feedback.
-
I also tried jamming twingate headless client setup into terraform container itself via the exposed TERRAFORM_PRE_RUN. Trying differnt commands / parts of: https://github.com/Twingate/github-action/blob/main/action.yml. I either run into libs/dependencies missing in bullseye or if I just do the basic install and |
Beta Was this translation helpful? Give feedback.
-
Ok, finally found a solution if anyone stumbles on this. This was the only thing that worked consistently for me and I preferred DrStrangeLove's answer in this stack link. Peace. ` #this is the way :P where x.x.x.x are actual IP addresses of nameservers you need to enforce
|
Beta Was this translation helpful? Give feedback.
Ok, finally found a solution if anyone stumbles on this. This was the only thing that worked consistently for me and I preferred DrStrangeLove's answer in this stack link. Peace.
` #this is the way :P where x.x.x.x are actual IP addresses of nameservers you need to enforce