-
Notifications
You must be signed in to change notification settings - Fork 8
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
Use a context for storing the environment config #29
Comments
Ideally, the tool would remain usable without additional files on the filesystem. This facilitates use with containers (both in a Tekton pipeline, as a podman/docker run, etc) without needing to mount a config file into the container every run. In order to simplify working with various different 3scale tools, I'm planning to allow 3scale-cms to read 3scalerc.yml files in the format of 3scale-toolbox. Then this cms tool could also follow the pattern of 3scale-toolbox in allowing the remote server to still be specified on the command-line as an option. |
Using a config file in the toolbox style or another makes it easier for people to use the interactive mode. I think for docker and container, even looking for the env variables The order of usage would be:
|
Use a config file to store the information regarding PROVIDER_KEY, PROVIDER_DOMAIN information, and add the command like
config
,set context
, andcurrent-context
The text was updated successfully, but these errors were encountered: