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

NameRule is inconvenient for Secrets like ENV_VAR #378

Open
webdeb opened this issue May 5, 2024 · 0 comments
Open

NameRule is inconvenient for Secrets like ENV_VAR #378

webdeb opened this issue May 5, 2024 · 0 comments
Assignees

Comments

@webdeb
Copy link

webdeb commented May 5, 2024

`Invalid component name "${args.name}". Component names must start with an uppercase letter and contain only alphanumeric characters.`,

its convenient to load secrets from env files, where the names often contain underscores, this rule screws it up, when you try to deploy the app, AFTER the secrets where loaded & setted from a file via sst secret load ./.env.

@webdeb webdeb changed the title Rule is not inconvenient for Secrets Rule is inconvenient for Secrets May 5, 2024
@webdeb webdeb changed the title Rule is inconvenient for Secrets NameRule is inconvenient for Secrets for ENV_VAR May 5, 2024
@webdeb webdeb changed the title NameRule is inconvenient for Secrets for ENV_VAR NameRule is inconvenient for Secrets like ENV_VAR May 5, 2024
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