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
Since #2437 the skaffold.yaml can have a metadata.name field. With upcoming changes for configurable kubecontext, this name-field needs to be set when creating a project-kubeContext relation (see #2384 (comment) for details).
So far, skaffold init is completely ignorant about this field, but I think we can make our users' lives easier if init takes care of the name field. There are two basic options:
Prompt the user for a name (with a suggestion). The downside here is that skaffold init will obviously require more user interaction.
Provide a sane default without prompting the user.
Both options need a sane default. A reasonable default value could be to use the directory basename of the current working dir.
So what do you think? Should skaffold init do that, and what should be the default?
The text was updated successfully, but these errors were encountered:
yeah I think we should try and have as little user input in skaffold init as possible. i'm fine with putting a default in, your suggestion of the current directory basename seems reasonable to me.
Since #2437 the
skaffold.yaml
can have ametadata.name
field. With upcoming changes for configurable kubecontext, this name-field needs to be set when creating a project-kubeContext relation (see #2384 (comment) for details).So far,
skaffold init
is completely ignorant about this field, but I think we can make our users' lives easier ifinit
takes care of the name field. There are two basic options:skaffold init
will obviously require more user interaction.Both options need a sane default. A reasonable default value could be to use the directory basename of the current working dir.
So what do you think? Should
skaffold init
do that, and what should be the default?The text was updated successfully, but these errors were encountered: