New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

AWS-dependent functions should fail gracefully when not running in AWS #26

Closed

hairyhenderson opened this issue Mar 28, 2016 · 1 comment

Labels

bug

Owner

hairyhenderson commented Mar 28, 2016

So uh... this happens:

$ echo '{{ec2dynamic "instance-identity/document" "unknown"}}' | ./gomplate
2016/03/27 22:40:39 Failed to GET from http://169.254.169.254/latest/dynamic/instance-identity/document: Get http://169.254.169.254/latest/dynamic/instance-identity/document: dial tcp 169.254.169.254:80: i/o timeout

I would've expected this:

$ echo '{{ec2dynamic "instance-identity/document" "unknown"}}' | ./gomplate_darwin-amd64 
unknown

hairyhenderson added the bug label

Owner Author

hairyhenderson commented Mar 28, 2016

Just to be clear - it takes like 30s for that error to happen... The timeout isn't so much a problem as the result.

hairyhenderson mentioned this issue

Using defaults on network errors and timeouts #27

Merged

hairyhenderson closed this as completed in #27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment