The protection_bypass_for_automation_secret field isn't available on the vercel_project data source

[vihangm]

When you have a project resource and set the protection_bypass_for_automation field, the protection_bypass_for_automation_secret field is populated so that one can reference it later.

We have two separate terraform environments where we need to use the protection_bypass_for_automation_secret field to populate a k8s secret, normally I'd create the project resource in one environment and then import it via the vercel_project data source in the other environment, however the data source doesn't expose the secret making this more challeging.

[dglsparsons]

Hi @vihangm, thanks for raising this. However, this is how the API functions by design - the field can only be read at creation time as it is sensitive. If you wish to store it to share between many different places, i'd suggest finding a place to store sensitive data.

[DavidS-ovm]

@dglsparsons why is it then available through the web UI? This only means that the API and terraform provider are a second class citizens in the ecosystem that can't detect when the value needs an update because someone manually changed it through the UI to a value the rest of (my) system does not know.

[DavidS-ovm]

Specifically

returns

with the bypass secret in clear text.