Skip to content
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

Better tools for environment variables #667

Closed
hadley opened this issue Feb 13, 2023 · 2 comments · Fixed by #794
Closed

Better tools for environment variables #667

hadley opened this issue Feb 13, 2023 · 2 comments · Fixed by #794
Labels
deploy ⛹️ feature a feature request or enhancement

Comments

@hadley
Copy link
Member

hadley commented Feb 13, 2023

  • Upload selected env vars on first release (avoid fail on first deploy problem)
  • Scan all projects and list which env vars are used (particularly needed when credentials get rolled)

(These are both somewhat bandaids over bigger auth issues but I think they're worth doing)

@hadley hadley added feature a feature request or enhancement deploy ⛹️ labels Feb 21, 2023
@hadley
Copy link
Member Author

hadley commented Mar 2, 2023

Should record env vars to update in the deployment record; that way if we implement a dry run feature, we could copy only those env vars to the dry environment.

@hadley
Copy link
Member Author

hadley commented Mar 22, 2023

Currently env vars are only supported on Posit connect, so don't need to worry about other end points yet.

hadley added a commit that referenced this issue Apr 18, 2023
* Extract `findDeployment()` helper. Fixes #801
* Read/write `envVars` in deployment record
* New `envVars` argument to `deployApp()`
* New `listServerEnvVars()` and `updateServerEnvVars()` to list/update env vars en masse.

Fixes #667.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deploy ⛹️ feature a feature request or enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant