Luke Hodkinson 3dc23b96ac Add a metadata provider for Vultr ...

Vultr uses a very similar approach to AWS, including using the
same IP address for serving metadata. In fact, it seems
as though if AWS appears first in the list of providers, that
provider mistakenly believes to be running on AWS (hence the
insertion of `NewVultr` in between GCP and AWS. I don't believe
AWS servers will accidentally try to use the Vultr provider,
as it seems that the `/v1/` endpoint doesn't exist on AWS.

Signed-off-by: Luke Hodkinson <furious.luke@gmail.com>

2017-06-24 07:43:07 +10:00

..

.gitignore

…

Dockerfile

Update for new default namespaces

2017-05-30 15:06:30 +01:00

main.go

Add a metadata provider for Vultr

2017-06-24 07:43:07 +10:00

Makefile

Simplify Makefiles for Packages

2017-06-22 12:40:03 +01:00

provider_aws.go

Added more AWS metadata to /var/config

2017-06-10 10:54:43 -04:00

provider_cdrom.go

…

provider_gcp.go

metadata: Simplify the GCP SSH code

2017-04-12 16:19:24 +01:00

provider_vultr.go

Add a metadata provider for Vultr

2017-06-24 07:43:07 +10:00