-
Notifications
You must be signed in to change notification settings - Fork 45
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
Fix the fact that some GCP env vars are immune to WithDisallowEnvVars #250
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@@ -23,7 +23,6 @@ const ( | |||
// TestGcpKeyIdAfterConfig will test the result of calling the wrapper's KeyId() | |||
// after it's configured with various options | |||
func TestGcpKeyIdAfterConfig(t *testing.T) { | |||
t.Parallel() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was removed as it didn't play nice with the new test case disabling env-vars
} | ||
|
||
func TestGcpCkmsSeal(t *testing.T) { | ||
t.Setenv(EnvGcpCkmsWrapperProject, "") // Make sure at least one required value is not set. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test worked correctly if it ran by itself but running them all together, if another test ran first and set the appropriate vars would fail as we wouldn't get the failure we expected.
No description provided.