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
{{ message }}
This repository has been archived by the owner on Jun 29, 2023. It is now read-only.
Originally posted by @rupertchen on pre-OSS repository
Context
As a user of KDT, whenever I want to run a deploy I have to pass as command line args: the build, context, artifact, etc., am I forgetting something?Basically, there are too many flags I need to pass to make a deploy, and most of the time I am using the same flags for a specific deploy (i.e. normal deploy to prod always uses the same 4/5 flags, why do I have to specify them every time).What I would like is some way to specify my default flags for a deployment (ex. in some yaml) so that I can say something like
kdt deploy production
and that would be the equivalent of passing all the flags I normally use to specify a production deploy.
Request
I should still be able to pass command line flags together with this new system, and command line flags would override the defaults.
Acceptance Criteria
enable new/current users to use kdt without having to discover somehow what all the required flags are.
Hints
interactive mode? That asks for required flags?
Add docs that tell you exactly what you need to run commands?
man-page like docs for kdt. At least for kdt deploy
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Originally posted by @rupertchen on pre-OSS repository
Context
As a user of KDT, whenever I want to run a deploy I have to pass as command line args: the build, context, artifact, etc., am I forgetting something?Basically, there are too many flags I need to pass to make a deploy, and most of the time I am using the same flags for a specific deploy (i.e. normal deploy to prod always uses the same 4/5 flags, why do I have to specify them every time).What I would like is some way to specify my default flags for a deployment (ex. in some yaml) so that I can say something like
and that would be the equivalent of passing all the flags I normally use to specify a production deploy.
Request
I should still be able to pass command line flags together with this new system, and command line flags would override the defaults.
Acceptance Criteria
enable new/current users to use kdt without having to discover somehow what all the required flags are.
Hints
kdt deploy
The text was updated successfully, but these errors were encountered: