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

Cloudflare apiToken as Secret & Allow to execute sst secret set without running sst.config.ts #377

Open
webdeb opened this issue May 5, 2024 · 3 comments
Assignees

Comments

@webdeb
Copy link

webdeb commented May 5, 2024

  1. It would be convenient to provide the Cloudflare Api Token as Secret, but its not possible because the app(input) function should not use sst Ressources, so its unclear how to deal with it, other then providing those values through the cli.

  2. problem is when you try to set secret and you have for example cloudflare configured as a second provider, sst tries to load the config and you have to pass environment variables to authenticate cloudflare. But you only want to set a secret on a stage, nothing more. This should be more or less unrelated, as far as I understand it only requires the static configuration of sst.config.ts like name, home etc.

Copy link
Contributor

thdxr commented May 6, 2024

yeah this is a good point - let me see if we can do less

@thdxr thdxr self-assigned this May 6, 2024
Copy link
Contributor

thdxr commented May 6, 2024

although for your first question - you should not be using sst.Secrets for provider values - there's too many weird situations that creates if we tried to make that work

those should be provided through normal env variables

@webdeb
Copy link
Author

webdeb commented May 6, 2024

should be provided through normal env variables

👌 yeah I've found it later, and then the 2nd issue is not painful anymore. After solved that I stumbled over the forced CamelCase issue #378 , which hurts much more, had then written a custom script to parse camelize and set env vars.

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

No branches or pull requests

2 participants