8 Commits (5d894e4ffda759cf269171d4f5d692a768a4e270)

Author	SHA1	Message	Date
George Christou	61277c0dbd	website/docs: Run `terraform fmt` on code examples (#12075) ... * docs/vsphere: Fix code block * docs: Convert `...` to `# ...` to allow `terraform fmt`ing * docs: Trim trailing whitespace * docs: First-pass run of `terraform fmt` on code examples	9 years ago
Ollie Ford	ed2b959f7e	Fix contradiction in terms with provider documentation (#10815) (#10874) ... * Remove contradiction with Scaleway documentation The parameters previously termed by Terraform: 1. Organization 2. Access key Are referred to, respectively, by Scaleway [0] as: 1. Access key 2. Token which is a confusing contradiction for a user. Since Scaleway terms (1) both 'access key' [0] and 'organization ID' [1], @nicolai86 suggested keeping the latter as already used, but changing (2) for 'token'; removing the contradiction. This commit thus changes the parameters to: 1. Organization 2. Token Closes #10815. [0] - https://cloud.scaleway.com/#/credentials [1] - https://www.scaleway.com/docs/retrieve-my-organization-id-throught-the-api * Update docs to reflect Scaleway offering x86 Scaleway now provides x86 servers [0] as well as ARM. This commit removes 'ARM' from various references suggesting that might be the only option. [0] - https://blog.online.net/2016/03/08/c2-insanely-affordable-x64-servers/	9 years ago
Raphael Randschau	98d84680b7	provider/scaleway server volume property (#9695) ... * provider/scaleway: extract volume validation helpers * provider/scaleway: add server volume property fixes #9499 * provider/scaleway: update `scaleway_server` docu * provider/scaleway: fix volume handling this actually broken when merging the latest SDK update :( * provider/scaleway: fix volume attachment * provider/scaleway: fix volume expectation	10 years ago
James Nugent	fc2d973e26	Merge pull request #9387 from nicolai86/feat/scaleway-import ... provider/scaleway: add support for importing resources	10 years ago
Raphael Randschau	fc4c848778	provider/scaleway: add importer support	10 years ago
Raphael Randschau	5cba23bf7b	provider/scaleway: fix headline in docs	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