DEVELOPER.md

Development Setup

If you want to contribute to the Terraform provider, be aware of the contribution guidelines available in this repository.

First, you need to setup your development environment. The following sections describe the options that you have.

Local Setup

Ensure you have the following tools installed on your local machine.

• git
• go
• golangci-lint
• make
• terraform

MacOS (Homebrew)

If you run on MacOS, you can use homebrew to speed up the installation process:

brew install git golang golangci-lint make terraform

Windows (Chocolatey)

Windows users can let chocolatey take over the installation for them:

choco install git golang golangci-lint make terraform

Configuration of the Terraform CLI

Next you need to setup local development overrides in the Terraform CLI according to this documentation. Once in place, Terraform will only consider local development builds for this provider.

Keep in mind that the configuration file location depends on your operating system:

• Mac/Linux/WSL: ~/.terraformrc
• Windows: %APPDATA%/terraform.rc

The configuration should look similar to this:

provider_installation {
  dev_overrides {
    "SAP/cloudfoundry" = "/path/to/go/bin" # the GOBIN directory can be found in the folder which `go env GOPATH` returns
  }

  direct {}
}

• Check the Local Authentication for supported login mechanisms.

Cloning of the Repository

The last step is then to clone the repository on your machine via:

git clone https://github.com/SAP/terraform-provider-cloudfoundry.git

Navigate into the directory of the cloned repository.

Install the Terraform Provider for Cloudfoundry Locally

Run the following command to build and install the provider:

make install

Verify the Setup

Next, we verify that Terraform has access to your local build of the provider. Navigate to the folder examples/provider/:

cd examples/provider/

To verify the setup, execute the terraform validate command:

terraform validate

If the setup was successful you should see the following message:

╷
│ Warning: Provider development overrides are in effect
│ 
│ The following provider development overrides are set in the CLI configuration:
│  - SAP/cloudfoundry in /go/bin
│ 
│ The behavior may therefore not match any released version of the provider and applying changes may cause the state to become incompatible with published releases.
╵
Success! The configuration is valid, but there were some validation warnings as shown above.

In case of errors, please check first that you executed the previous steps correctly. If you are still stuck, feel free to ask for support by raising a question in the GitHub Discussions of this repository.

Note: Be aware that when using the development override you must not use the terraform initcommand. It is not necessary and may error unexpectedly. Refer authentication to login to the environment.

Dev Container

Note: In order to use dev containers, you must have a container runtime up and running on the machine. For details, we refer to the official documentation about Developing inside a Container.

First, you must clone the repository:

git clone https://github.com/SAP/terraform-provider-cloudfoundry.git

Then open the cloned repository in Visual Studio Code. Within Visual Studio Code, press the "Open a remote Window" button in the lower left corner:

Visual Studio Code will open the command palette. Choose the option "Reopen in Container":

This will trigger the start of the dev container. You can choose to open a dev container with two configurations:

• "Terraform provider for Cloudfoundry - Development" - the configuration in .devcontainer/devcontainer.json contains the development override for the Terraform provider so that the local build is used.

Note: In the first run, the download of the container might take a while, so maybe time to grab a cup of coffee ☕. Refer authentication to login to the environment.

GitHub Codespaces

Step 1: Open the repository in GitHub Codespaces via the button:

Step 2: There is no step 2 😎.

Note: Refer authentication to login to the environment.

Howto Commit

Once you're done applying changes to the cloned repository, please ensure that the tests can still be executed (by running make test) and that the documentation is up to date (by executing make generate). Afterwards you're encouraged to open a pull-request to this repository. Please be aware that we're following the conventional commits specification, which means the pull-request title has to be structured in a certain way:

• fix: typo in the documentation
• feat: new resource xyz added
• refactor!: aligning schemas

For more examples, please have a look in the conventional commits specification.