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

Version 2 roadmap #125

Open
QuentinBrosse opened this issue May 20, 2019 · 12 comments
Labels

Comments

@QuentinBrosse
Copy link
Collaborator

@QuentinBrosse QuentinBrosse commented May 20, 2019

Dear Cloud Rider,

In order to improve our provider and support our new products we will make a significant refactoring on the whole codebase to finally release a version 2.

Naturally, we are taking the backward compatibility issues very seriously. Therefore we will follow a process designed to make it possible for you to execute a smooth transition from your current version to the v2.

Roadmap

Step 1: New minor versions [Non-Breaking Change]

This version will deprecate some elements of this provider but will not create any breaking change. It will allow you to prepare your configuration for the v2 without breaking your actual configuration.

Here is a list of actions we will take - all the details will be discussed in there dedicated sub-issue:

v1.10.0: milestone

  • Update the terraform SDK to 0.12 [#124]
  • Fix all acceptance tests [#126]

v1.11.0: milestone

  • Refactor the internal meta interface to prepare the transition to our new Go SDK [#131]
  • Update the provider schema and introduce the new Scaleway configuration (it will be consistent between all our developer tools) [#140]
  • Rename all current resources following this scheme scaleway_{product}_{resource}. The old resources will be kept but deprecated. This will allow the creation of resources for our new products [#143]
  • Add baremetal resources [#241, #228]
  • Tests

v1.12.0: milestone

  • Add k8s beta resources [#258]
  • Add lb resources (lb, backend, frontend) [#278, #284, #305 ]
  • Bug fixes and minor features (more infos)

v1.13.0: milestone

  • Add lb backend healthcheck [#309]
  • Add lb certificates [#310]
  • Rework all scaleway data sources [#225]
  • Add registry resource [#tba]
  • Add database resource [#tba]

Step 2: New major version v2.0.0 milestone

The version will clean all the deprecated elements introduced in the v1.10.X.

Here is a list of actions we will take - all the details will be discussed in there dedicated sub-issue:

  • 1. Remove deprecated provider schema fields [#tba]
  • 2. Remove deprecated configuration file and environment variables [#tba]
  • 3. Remove deprecated resources (mainly for the instance product) [#tba]
  • 4. Change the configuration precedence [#tba]
@balupton

This comment has been minimized.

Copy link

@balupton balupton commented May 31, 2019

Now that terraform 0.12 support has landed can a release be made for that, with the rest of the stuff above being in an additional release. As the 0.12 support is quite urgent to get out to users

@QuentinBrosse

This comment has been minimized.

Copy link
Collaborator Author

@QuentinBrosse QuentinBrosse commented May 31, 2019

@balupton we are totally agree with you. We will release a new minor version next week :)

@QuentinBrosse

This comment has been minimized.

Copy link
Collaborator Author

@QuentinBrosse QuentinBrosse commented Jun 4, 2019

@balupton Hi,

The v0.10.0 is now released! :)

@hazcod

This comment has been minimized.

Copy link

@hazcod hazcod commented Aug 18, 2019

So I was trying to use terraform to setup VC1S instances, but those are not instrumentable by API according to support for stock reasons... (API always returns Quota reached for every instance)

Is there an ETA for this provider for the new instances, since it's unuseable right now?
Or would v0.10.0 provide a new instance type?

@jerome-quere

This comment has been minimized.

Copy link
Collaborator

@jerome-quere jerome-quere commented Aug 20, 2019

Hello @hazcod when using v1.10.0 you can use type parameter to select a server type (https://www.terraform.io/docs/providers/scaleway/r/server.html#type). You can find availables server types in our web console (https://console.scaleway.com/instance/servers/create).

@hazcod

This comment has been minimized.

Copy link

@hazcod hazcod commented Aug 20, 2019

Can confirm it works with DEV1-S instead of VC1S.

@QuentinBrosse

This comment has been minimized.

Copy link
Collaborator Author

@QuentinBrosse QuentinBrosse commented Oct 2, 2019

Hi,

The v0.11.0 is now released! 🎉

@mdawar

This comment has been minimized.

Copy link

@mdawar mdawar commented Oct 10, 2019

Hi, I have a question please about the new changes, the scaleway_instance_server resource doesn't seem to have a way to get the public IPv6 address, in version 0.10 we had public_ipv6 but starting version 0.11 we only have public_ip for the IPv4 only, any way to get the IPv6 address in the new version?

@QuentinBrosse

This comment has been minimized.

Copy link
Collaborator Author

@QuentinBrosse QuentinBrosse commented Oct 11, 2019

Hi @mdawar,
Thanks for reporting it!

I just created an issue to expose a public_ipv6 attribute on the scaleway_instance_server resource. It will be released in the v1.12.0. 🙂

@mdawar

This comment has been minimized.

Copy link

@mdawar mdawar commented Oct 11, 2019

Hi @QuentinBrosse, thanks for the quick response, I have another question please, why the scaleway_ssh_key resource will be removed in v2? I don't think that it's better to upload the keys in the console as suggested by the migration guide, being able to manage everything using Terraform is critical especially in cases where everything is automated, this is going to make a step backward in my opinion, all the other cloud providers provide a way to manager SSH keys using Terraform.

@QuentinBrosse

This comment has been minimized.

Copy link
Collaborator Author

@QuentinBrosse QuentinBrosse commented Oct 18, 2019

Hi @mdawar,
The scaleway_ssh_key is deprecated and will be removed in v2.0. This resource is replaced by the new scaleway_account_ssh_key. You can find this info in the deprecated scaleway_ssh_key.

I just see that the migration guide is not up to date. I have just created #287 to fix it, sorry for the inconvenience.
cc @hazcod @gmile

@QuentinBrosse

This comment has been minimized.

Copy link
Collaborator Author

@QuentinBrosse QuentinBrosse commented Oct 28, 2019

Hi,

The v0.12.0 is now released! 🎉

Changelog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.