install
- will install all required artifacts into a working
changes. it will not alter the configuration [of OpenShift or
Kubernetes] via a provider. a deployment guy will be able to configure
the deployment process, which will be started by run
.
run
- will deploy artifacts and their configuration via the provider
onto the platform. configuration will become effectice and the
application will be available to users.
stop
- will disable access to the application for users. configuration
will remain deployed to the platform but not be effective.
uninstall
- artifacts will be removed from the platform
The tool used to maintaine an Atomic App will not take care about cleaning up the current directory. It will also try to keep the pollution minimal, eg not unpack more than nessecary [to configure the application’s artifacts] into the current directory.
Crazy idea - what if we propose addition of arbitrary verbs to
atomic
via labels?atomic unpack
io.projectatomic.atomic.cmd.unpack=.*
unpack
itself is kinda specific to our use case and I don't see it very well acceptable foratomic
's generic use case. But being able to define own commands might be the right way