这是indexloc提供的服务,不要输入任何密码
Skip to content

Validate sensitive environment variable config when creating env vars #185

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

Merged
merged 2 commits into from
May 13, 2024

Conversation

dglsparsons
Copy link
Collaborator

Turns out the API elides non-sensitive values into being sensitive if
the team has a sensitiveEnvironmentVariablePolicy set on it.

To prevent this from causing provider issues when the sensitive field
is explicitly set to false, warn at plan time that the resource being
created does not match the team policy.

Closes #183

@dglsparsons dglsparsons force-pushed the dgls/sensitive-env-policy branch from effb63a to 2ae931a Compare May 13, 2024 13:07
Turns out the API elides non-sensitive values into being sensitive if
the team has a sensitiveEnvironmentVariablePolicy set on it.

To prevent this from causing provider issues when the `sensitive` field
is explicitly set to `false`, warn at plan time that the resource being
created does not match the team policy.

Closes #183
@dglsparsons dglsparsons force-pushed the dgls/sensitive-env-policy branch from 2ae931a to 9c121b1 Compare May 13, 2024 14:11
@dglsparsons dglsparsons enabled auto-merge (squash) May 13, 2024 15:49
@dglsparsons dglsparsons merged commit 1762a94 into main May 13, 2024
@dglsparsons dglsparsons deleted the dgls/sensitive-env-policy branch May 13, 2024 15:59
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.

Can't create non-sensitive vercel_project_environment_variable
2 participants