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

space: run space init in github e2e job #378

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

Conversation

sttts
Copy link
Contributor

@sttts sttts commented Sep 26, 2023

Smoke test for up space init. To be extended, e.g. moved into a real test suite.

@sttts sttts force-pushed the sttts-e2e-init branch 2 times, most recently from ae211c1 to 5411d20 Compare September 26, 2023 21:28
@@ -31,8 +31,8 @@ type authorizedRegistryFlags struct {
registryFlags

TokenFile *os.File `name:"token-file" help:"File containing authentication token."`
Username string `hidden:"" name:"registry-username" help:"Set the registry username."`
Password string `hidden:"" name:"registry-password" help:"Set the registry password."`
Username string `hidden:"" name:"registry-username" env:"UPBOUND_REGISTRY_USERNAME" help:"Set the registry username."`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we'll need to adjust the logic in

if p.TokenFile == nil && p.Username == "" && p.Password == "" {
a little to get this to work 👍

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't think so. Having those env vars should be enough.

e2e-tests:
runs-on: ubuntu-20.04
#runs-on:
# group: managed-control-planes-testing
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given that we're just installing spaces and not creating control planes, we may not need this yet.

--yes
env:
UPBOUND_REGISTRY_USERNAME: ${{ secrets.DOCKER_USR }}
UPBOUND_REGISTRY_PASSWORD: ${{ secrets.DOCKER_PSW }}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tnthornton is this supposed to work? Do these variables exist? I lack permissions to see the secrets in the repo and the org.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sttts they appear to. (both on the settings page and because 'login to docker' passed in main https://github.com/upbound/up/actions/runs/6318356855/job/17157170338).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh you know what, those creds are probably not available to PRs from forks.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh you know what, those creds are probably not available to PRs from forks.

This is the case. GH does not allow forks to use the creds to prevent malicious PR's from exfiltrating secrets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants