Allow GCP hosted clusters to be deployed

[d-nagy]

Fix for issue #23

[jamesrwilkinson]

We'll want to remove this from the validation but this alone won't allow for GCP hosted clusters to be deployed. We would get an error as the GCP disk storage type PD-SSD is not included in the enum V3StorageType in the api client.

We will need to update the Go API client to support the new GCP resources added in the API.

I'll regenerate the api client from the latest api spec - we might also need to make some changes inside of the hosted cluster resource.

[d-nagy]

Ah, thanks for the information @JamesWilkinsonCB, that makes sense. I forgot about the disk changes.

One thing too is that for PD-SSDs we cannot specify IOPS - we'd need to check how the API handles this (whether we can just specify 0 or whether we need to omit the IOPS parameter entirely)

[jamesrwilkinson]

One thing too is that for PD-SSDs we cannot specify IOPS - we'd need to check how the API handles this (whether we can just specify 0 or whether we need to omit the IOPS parameter entirely)

I think we will want to omit this parameter as it looks like it's no longer a required field. We can also remove the required tag from this field in the Schema.

I've regenerated the client in this PR, which will allow us to add GCP support to the provider.

[amalucelli]

I don't think using local works here:

» ls -1 ~/.terraform.d/plugins/local/couchbasecapella/1.0.0/
darwin_amd64

» cat versions.tf
terraform {
  required_providers {
    couchbasecapella = {
      source  = "local/couchbasecapella"
      version = "1.0.0"
    }
  }
}

» terraform init

Initializing the backend...

Initializing provider plugins...
- Finding local/couchbasecapella versions matching "1.0.0"...
╷
│ Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider local/couchbasecapella: provider registry registry.terraform.io does not have a provider named
│ registry.terraform.io/local/couchbasecapella

IIRC the hostname when building locally is kind of required. If you omit it, it will use the default registry and it fails:

If hostname is omitted, Terraform will use the Terraform Registry hostname as the default hostname.

Usually setting this to github.com is a good practice, as it matches the hostname/namespace from the repository on GitHub.

Also, the folder needs to be created first, maybe we can set up in another PR a target on the Makefile to automate this and improve the development flow (I can help with this)?

[jamesrwilkinson]

Yeah I agree, that would be much better in the Makefile. We can just run the one command then. I'll create a branch off of this one and we can make a PR for Makefile/changes to docs

[jamesrwilkinson]

I've fixed the issue with the commands listed for building the provider in the README - I'll create a new PR for the changes to the Makefile that can automate this.