Skip to content
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.

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

Use the aws-sdk-go instance metadata client #2728

Closed
wants to merge 1 commit into from
Closed

Use the aws-sdk-go instance metadata client #2728

wants to merge 1 commit into from

Conversation

jen20
Copy link
Collaborator

@jen20 jen20 commented Sep 10, 2015

Remove the instance metadata client originally introduced with the change from goamz to aws-sdk-go in favour of the one recently introduced to aws-sdk-go which supports retries.

This is as per the discussion on the original conversion from goamz at #2034.

Remove the instance metadata client originally introduced with the
change from goamz to aws-sdk-go in favour of the one recently introduced
to aws-sdk-go which supports retries.
@jen20
Copy link
Collaborator Author

jen20 commented Sep 10, 2015

This should also help resolve some of the issues seen in #1539. The build is currently appearing broken on this branch because of the Google Compute Engine builder, fixed in #2729.

func (c *AccessConfig) Region() (string, error) {
if c.RawRegion != "" {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't believe this code should have been removed. Region() is used by non-chroot builders which do not have access to the metadata.

@rickard-von-essen
Copy link
Collaborator

This is probably obsolete. I'll try to check.

@rickard-von-essen
Copy link
Collaborator

This has been osolete by later changes.

@ghost
Copy link

ghost commented Apr 3, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@hashicorp hashicorp locked and limited conversation to collaborators Apr 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants