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
I often use a different CLI profile for each LangStream environment, local dev, remote test, and remote production. In most cases, I use a different infrastructure and secrets file for each of those profiles with a name like secrets-prod.yaml. It would be handy to be able to associate a default infra and secrets file with the CLI profile I am using. Then I would be able to deploy/update my app without having to specify those options. Of course, I would want to be able to override the default with the command line options.
A few thoughts on how this might work:
A set command that accepts an infra/secrets file and saves it as part of my profile
A get command to retrieve the default files so I can view them or save them as a file
An edit command would let me edit the default file in place (nice to have)
A mechanism to specify the file in base64 encoding so it can be completely specified using a command line (for automation tooling, nice to have)
The text was updated successfully, but these errors were encountered:
I often use a different CLI profile for each LangStream environment, local dev, remote test, and remote production. In most cases, I use a different infrastructure and secrets file for each of those profiles with a name like
secrets-prod.yaml
. It would be handy to be able to associate a default infra and secrets file with the CLI profile I am using. Then I would be able to deploy/update my app without having to specify those options. Of course, I would want to be able to override the default with the command line options.A few thoughts on how this might work:
The text was updated successfully, but these errors were encountered: