Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Please consider notion of 'init container' for devfile #69

Open
RickJWagner opened this issue Feb 15, 2021 · 1 comment
Open

Please consider notion of 'init container' for devfile #69

RickJWagner opened this issue Feb 15, 2021 · 1 comment

Comments

@RickJWagner
Copy link

Devfiles are used by Che and CodeReady Workspaces. Some users have sophisticated needs that would benefit from some scripted initialization.

Example: A Che user wants to do a Java/Maven build with a custom settings.xml file (very common). Per the product documentation, a Secret can be used to mount the settings.xml file. The user wants to supply the Secret as an early step in the Workspace creation. (Currently, there is no opportunity to do this through a devfile-created workspace. The workspace will start before the user has a chance to make a Secret, thus this path to getting a custom settings.xml file is unavailable.)

Please help by considering allowing some notion of an 'init container' or other ordering or prioritization for some directives so initializations can be done.

@sparkoo
Copy link
Member

sparkoo commented Feb 18, 2021

Is this for devfile v1 or v2? In case of v1, I think this issue belongs to https://github.com/eclipse/che/issues, in case of v2 it should go to https://github.com/devfile/api/issues

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants