aws-ia
GOPROXY=direct specification causes taskcat failures when using the container outside of AWS networks
Describe the bug In several templates my QuickStart depends on, the variable GOPROXY=direct has been set.
This fails when using the taskcat container. In talking with @troy-ameigh this appears to have been inserted to help with some restrictions on AWS networks so it seems to work fine as a container or in AWS CI.
I personally encounter it is these places:
https://github.com/aws-quickstart/quickstart-amazon-eks-cluster-resource-provider/blob/d38dc2beb3c1127e1332853dc9cbfcb1910b28d9/Dockerfile#L11-L13
https://github.com/aws-quickstart/quickstart-helm-resource-provider/blob/ec2d91bcb645a38d3aba8956fb90434d5b34de7e/Dockerfile#L11-L13
To Reproduce Steps to reproduce the behavior:
- Run taskcat while only connected to the internet and use the EKS quickstart.
- After failure remove 'GOPROXY=direct` and it succeeds.
Fails with:
Expected behavior The source files should either work both inside and outside AWS networks or there should be a variable that can be set to disable this setting.
Screenshots If applicable, add screenshots to help explain your problem.
Manual build:
**Version (Please make sure you are running the latest version of taskcat)
- Taskcat Version (ex: [2018.817.210357])
Note: Python Version (python3 required)
To find versions:
Via taskcat: taskcat -V
Via pip3: pip3 show taskcat
Note: both version should match
To update taskcat run:
for docker : docker pull taskcat/taskcat
for pip3: pip3 install --upgrade taskcat
Additional context Add any other context about the problem here.
