You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Applies overrides from the .env file binding Secrets to a different Cloud Secret Manager resource.
740
-
* For example, "&API_KEY=other@2" binds the value of /projects/1234/secrets/other/versions/2 to env var API_KEY and the secret param named API_KEY.
749
+
* Secrets references are of the form csm://secretName/version, referencing a Secret in the same project as the Endpoint.
750
+
* /version can be omitted and will cause the secret to resolve to whatever the latest version was at time of deploy.
741
751
*
742
752
* For each binding imported from the .env file,
743
753
* 1) TODO: Check if a conflicting SecretParam with the same name exists. If so, override the param so that the prompting flow will look in the right place when deciding whether or not to create a new Secret.
744
754
* 2) Upsert the binding directly into the Build's SecretEnvVars, which will cause it to be actually available in process.ENV
0 commit comments