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

project_environment_variable values should be sensitive #71

@viki53

Description

@viki53

Hi,

I've started to use your provider earlier today and I'm having a few issues and questions.

My main issue is the difference of behavior between the vercel_project.environment block and the vercel_project_environment_variable resource: the first one marks all values as sensitive (which is good for security) but the later doesn't so I risk having values being output when I don't want them displayed.

I also find weird having to specify an id is the vercel_project.environment blocks, but I won't be using them as I much prefer having dedicated resources anyway.

Also, now that this new vercel_project_environment_variable resource exists, not specifying the environment property in a vercel_project shouldn't cause an update of the resource if I never had it specified before: this makes me think that every time I'll update a project property I risk breaking all my env vars and having to re-import them via the vercel_project_environment_variable resources, which I define in different TF runs (kind of like the architecture in #47).


Update: I tried applying the changes on my project and it did break all the env vars (including those that were defined in the same run using vercel_project_environment_variable resources) as I had feared… I had to re-add all of them.
This is not OK for a stable deployment process!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions