Skip to content

Latest commit

 

History

History
46 lines (29 loc) · 2.25 KB

CONTRIBUTING.md

File metadata and controls

46 lines (29 loc) · 2.25 KB
Raw

Contributing to the Pulumi ecosystem

Do you want to contribute to Pulumi? Awesome! We are so happy to have you. We have a few tips and housekeeping items to help you get up and running.

Code of Conduct

Please make sure to read and observe our Code of Conduct

Community Expectations

Please read about our contribution guidelines here.

Setting up your development environment

Pulumi prerequisites

Please refer to the main Pulumi repo's CONTRIBUTING.md file for details on how to get set up with Pulumi.

Committing Generated Code

You must generate and check in the SDKs on each pull request containing a code change, e.g. adding a new resource to resources.go.

  1. Run make build_sdks from the root of this repository
  2. Open a pull request containing all changes
  3. Note: If a large number of seemingly-unrelated diffs are produced by make build_sdks (for example, lots of changes to comments unrelated to the change you are making), ensure that the latest dependencies for the provider are installed by running go mod tidy in the provider/ directory of this repository.

Running Integration Tests

The examples and integration tests in this repository will create and destroy real GCP cloud resources while running. Before running these tests, make sure that you have configured Pulumi with GCP successfully once before.

You need to set these environment variables before running the integration tests:

  1. GOOGLE_PROJECT - The name of the project to deploy test resources into.
  2. GOOGLE_REGION - The name of the region to deploy test resources into.
  3. GOOGLE_ZONE - The name of the zone within the chosen region to deploy test resources into.

The integration tests do try to clean up after themselves by deleting everything that was created, but in the event of bugs or test failures you may need to go into the Google Cloud portal and delete resources yourself.

Once you have set all required environment variables and configured your GCP credentials, make test_all will run all integration tests.