ISSUE TYPE
Ansible creator generates a lot of sample configuration files upon initialization, with some being only vaguely related to the collection itself like devfile.yaml (which is only for k8s-testing).
Users might not need those files, but especially beginners might not know that this file is optional, and they could remove it from their collection without side-effects.
SUMMARY
Add options to en/dis-able config generation for non-required/optional integrations (and expose them in the VSCode integration as checkboxes, e.g.: '[ ] Generate Kubernetes files (devfile.yaml)', to signal to the user what this file does and if they need it.
While a lot of that information might be available on the docs, enabling users to not leave the editor to look up their purpose is helpful.
ISSUE TYPE
Ansible creator generates a lot of sample configuration files upon initialization, with some being only vaguely related to the collection itself like
devfile.yaml(which is only for k8s-testing).Users might not need those files, but especially beginners might not know that this file is optional, and they could remove it from their collection without side-effects.
SUMMARY
Add options to en/dis-able config generation for non-required/optional integrations (and expose them in the VSCode integration as checkboxes, e.g.: '[ ] Generate Kubernetes files (
devfile.yaml)', to signal to the user what this file does and if they need it.While a lot of that information might be available on the docs, enabling users to not leave the editor to look up their purpose is helpful.