Improvement: More feature flags for turning off/on creation of configuration files for optional tooling #363
Labels
documentation
Improvements or additions to documentation
Comments
|
I agree that not everyone is going to need the devfile or devcontainer, but I'm not sure we can remove the devfile since it's a hook into https://developers.redhat.com/products/openshift-dev-spaces/overview?source=sso. (which if you haven't used it, it's pretty cool) TBH, we're trying to stike a balance between all the users, local venv users, dev container users, RH devspaces users, and users of backstage with the ansible plugin. Will leave this open to get additional feedback from the community to help make a case for option containerized/web IDE scenarios. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: