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

dont attempt secrets lookup when org or project not set #2550

Merged
merged 1 commit into from
Jan 6, 2023

Conversation

alexcb
Copy link
Collaborator

@alexcb alexcb commented Jan 6, 2023

This fixes a bug where using VERSION --use-project-secrets 0.6 causes secrets to be lookedup in the cloud with an empty org or project, which returns an unauthorized error rather than the expected unable to lookup secret SECRET3: not found error message (which causes the +secrets-test test to fail).

Signed-off-by: Alex Couture-Beil alex@earthly.dev

This fixes a bug where using `VERSION --use-project-secrets 0.6` causes
secrets to be lookedup in the cloud with an empty org or project, which
returns an unauthorized error rather than the expected `unable to
lookup secret SECRET3: not found` error message (which causes the
`+secrets-test` test to fail).

Signed-off-by: Alex Couture-Beil <alex@earthly.dev>
@alexcb
Copy link
Collaborator Author

alexcb commented Jan 6, 2023

I'm torn between expanding our integration tests to catch this -- it's a growing issue where introducing feature flags cause a combinatorics-expansion of tests required to maintain full coverage.

When #2237 is released, we'll be updating this to be VERSION 0.7, which will flip it on (this was discovered while working on our initial RC in #2271)

@alexcb alexcb merged commit c6ed7b6 into main Jan 6, 2023
@alexcb alexcb deleted the acb/secrets-v0.7-fix branch January 6, 2023 17:00
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.

None yet

2 participants