Reserved folder for storing stack specific resource files #457
Labels
area/registry
Devfile registry for stacks and infrastructure
future
Items in consideration to be added to future spec levels
lifecycle/rotten
Rotten items. These items have been stale for 60 days and are now closed.
lifecycle/stale
Stale items. These items have not been updated for 90 days.
Background: #421
If a stack contains supporting resources that are required for the function of the stack, e.g. Dockerfiles in the future, the stack can store those supporting files as part of the devfile registry. However, there is currently no reserved location for storing those files. This means that when tools like odo when doing a component create, it may potentially overwrite user application files on a component create.
For example, if a stack contains a file
docker/Dockerfiles
under the stack folder in a registry, duringodo create
, it will clone the stack folder. If the user application already contains the same file, this clone may overwrite the user file. In order to avoid file collision between user application and files provided by the stack, we can resolve it by reserving a folder, e.g. .devfile or .stack, that allows a stack to store the stack supporting files.The registry will look something like this:
Note: If we have that, we can also consider putting the
devfile.yaml
under the.devfile
by default.The text was updated successfully, but these errors were encountered: