12 Commits (cdc3fa8337bd7a0be06bbd2fe2aee2fdbd17e4ec)

Author	SHA1	Message	Date
James Bardin	0220b83466	remove scaleway-cli package with borken deps ... github.com/scaleway/scaleway-cli/pkg/utils can be imported because it depends on github.com/moul/gotty-client which can't build on solaris. This requires removing the github.com/scaleway/scaleway-cli/pkg/api/helpers.go file which imports the utils package, and we don't use. Not sure how we'll handle this if the structure of the scaleway package changes and we can't break this import any longer.	9 years ago
James Bardin	359170d5d7	sync scaleway packages ... multiple scaleway-cli packages were out of sync, unfortunately this pulled in some other updates.	9 years ago
James Bardin	964253f139	Manually fix scaleway api package ... The scaleway api package depends transitively on the gotty-client package which is broken on solaris. Since it's only imported through the helpers.go file, and we don't call an functionality in that file, we can compile without it for now.	10 years ago
James Bardin	daa2b78a9c	need to add the files too	10 years ago
James Bardin	cfa299d2ee	Update deps in unknown state and rever nomad ... Nomad was manually updated, so revert that to the version in master, remove it from vendor.json and add it to the ignore list. Update all packages that were in an unknown state to their latest master commits.	10 years ago
James Bardin	a0b70b0ec7	Sync the vendor folder with the manifest ... A number of PRs have come through which modified the vendor folder without recording the proper information. This resets everything back to the recorded version.	10 years ago
Raphael Randschau	e5ff0f0cb2	provider/scaleway: update sdk (#9976) ... the SDK updates includes an fix for the image cache, which might lead to wrong images ids being returned on lookup...	10 years ago
Raphael Randschau	71fa8f171b	provider/scaleway: govendor integration (#9713)	10 years ago
Raphael Randschau	082ef04b9e	provider/scaleway: update sdk for ams1 region (#9687) ... * provider/scalway: update sdk for ams1 region * provider/scaleway typecast volume size as of 472a493	10 years ago
Raphael Randschau	85b982f26d	provider/scaleway: update go sdk ... scaleway is about to introduce multiple regions, so we anticipate this change by upgrading the API sdk to a version supporting regions	10 years ago
Raphael Randschau	9f314a3c29	provider/scaleway: Expose IPv6 support, improve documentation (#7784) ... * provider/scaleway: update api version * provider/scaleway: expose ipv6 support, rename ip attributes since it can be both ipv4 and ipv6, choose a more generic name. * provider/scaleway: allow servers in different SGs * provider/scaleway: update documentation * provider/scaleway: Update docs with security group * provider/scaleway: add testcase for server security groups * provider/scaleway: make deleting of security rules more resilient * provider/scaleway: make deletion of security group more resilient * provider/scaleway: guard against missing server	10 years ago
Raphael Randschau	9081cabd6e	Add scaleway provider (#7331) ... * Add scaleway provider this PR allows the entire scaleway stack to be managed with terraform example usage looks like this: ``` provider "scaleway" { api_key = "snap" organization = "snip" } resource "scaleway_ip" "base" { server = "${scaleway_server.base.id}" } resource "scaleway_server" "base" { name = "test" # ubuntu 14.04 image = "aecaed73-51a5-4439-a127-6d8229847145" type = "C2S" } resource "scaleway_volume" "test" { name = "test" size_in_gb = 20 type = "l_ssd" } resource "scaleway_volume_attachment" "test" { server = "${scaleway_server.base.id}" volume = "${scaleway_volume.test.id}" } resource "scaleway_security_group" "base" { name = "public" description = "public gateway" } resource "scaleway_security_group_rule" "http-ingress" { security_group = "${scaleway_security_group.base.id}" action = "accept" direction = "inbound" ip_range = "0.0.0.0/0" protocol = "TCP" port = 80 } resource "scaleway_security_group_rule" "http-egress" { security_group = "${scaleway_security_group.base.id}" action = "accept" direction = "outbound" ip_range = "0.0.0.0/0" protocol = "TCP" port = 80 } ``` Note that volume attachments require the server to be stopped, which can lead to downtimes of you attach new volumes to already used servers * Update IP read to handle 404 gracefully * Read back resource on update * Ensure IP detachment works as expected Sadly this is not part of the official scaleway api just yet * Adjust detachIP helper based on feedback from @QuentinPerez in https://github.com/scaleway/scaleway-cli/pull/378 * Cleanup documentation * Rename api_key to access_key following @stack72 suggestion and rename the provider api_key for more clarity * Make tests less chatty by using custom logger	10 years ago