knative
`func create`: persist --language choice
- Give users the option to save the runtime as default (y/n)
- Make sure to let them know where this is saved
- Make sure the template always defaults to -c when not provided as a flag (-t)
- Make sure to let them know where this is saved
I don't think that's a great idea. I think the user should just be able to run func config global. See: https://github.com/knative-sandbox/kn-plugin-func/issues/573#issuecomment-962003540
I will discuss this further with @lance this week, but the work I am doing on func invoke actually requires taking a bite out of the config situation: in particular opening the door to more conventional "config" settings, including git-like behavior of displaying a helpful message informing the user they need to choose a language, but can set a default via git config ... --global (exact syntax TBD)
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
To expand on this issue a bit, I was envisioning that the first time func is run, it will detect there is no user configuration, and the user will be prompted to run through a first-time setup, which is creating the global config (see #901). One of the questions asked of course being the user's preferred default language (if any).
Should be resolved in https://github.com/knative-sandbox/kn-plugin-func/issues/901
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.