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

Use single envvar to specify test org (PULUMI_TEST_OWNER) #98

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

justinvp
Copy link
Member

There are currently two envvars that are used to specify an Pulumi Service org for tests:

  1. The automation API tests look for the PULUMI_TEST_ORG envvar and fallback to using the pulumi-test org when the envvar isn't set. We're not currently setting PULUMI_TEST_ORG in the GHA workflows like we do in pulumi/pulumi, so presumably the automation API tests are using the pulumi-test org fallback.
  2. There's also a PULUMI_TEST_OWNER envvar that some of the integration tests uses. We are currently setting PULUMI_TEST_OWNER to moolumi.

This change updates the automation API tests to first look for the PULUMI_TEST_OWNER envvar, falling back to PULUMI_TEST_ORG, and then finally pulumi-test. That way, we only need to have a single consistent envvar set in CI (PULUMI_TEST_OWNER), set to moolumi, which is the org we want to use for these tests.

PULUMI_TEST_OWNER was chosen over PULUMI_TEST_ORG because PULUMI_TEST_OWNER is also used in the Go integration test framework.

There are currently two envvars that are used to specify an Pulumi Service org for tests:

1. The automation API tests look for the `PULUMI_TEST_ORG` envvar and fallback to using the `pulumi-test` org when the envvar isn't set. We're not currently setting `PULUMI_TEST_ORG` in the GHA workflows like we do in `pulumi/pulumi`, so presumably the automation API tests are using the `pulumi-test` org fallback.
2. There's also a `PULUMI_TEST_OWNER` envvar that some of the integration tests uses. We are currently setting `PULUMI_TEST_OWNER` to `moolumi`.

This change updates the automation API tests to first look for the `PULUMI_TEST_OWNER` envvar, falling back to `PULUMI_TEST_ORG`, and then finally `pulumi-test`. That way, we only need to have a single consistent envvar set in CI (`PULUMI_TEST_OWNER`), set to `moolumi`, which is the org we want to use for these tests.

`PULUMI_TEST_OWNER` was chosen over `PULUMI_TEST_ORG` because `PULUMI_TEST_OWNER` is also used in the Go integration test framework.
@justinvp justinvp added the impact/no-changelog-required This issue doesn't require a CHANGELOG update label Jan 31, 2023
@Frassle
Copy link
Member

Frassle commented Jan 31, 2023

PULUMI_TEST_OWNER was chosen over PULUMI_TEST_ORG because PULUMI_TEST_OWNER is also used in the Go integration test framework.

Do we consistently use the "owner" terminology for orgs everywhere else? I'd think trying to get everything consistently using "PULUMI_TEST_ORG" would be more understandable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/no-changelog-required This issue doesn't require a CHANGELOG update
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants