add verbs for infrastructure to Architecture

This commit is contained in:
ansgarz 2022-02-24 18:51:54 +01:00
parent 2d26bafe4d
commit 4c6d3ba3c3

View file

@ -35,7 +35,7 @@ package domain {
class Service { class Service {
cleanup (): means remove parts (install & configuration) to enable e.g. re-provision in some cases, results in an error otherwise. cleanup (): means remove parts (install & configuration) to enable e.g. re-provision in some cases, results in an error otherwise.
provision (): means install & configure. provision (): means install & configure.
install (): install packages, files but not configuration files. Fire & forget (re-) installation is posible. install (): install packages, files but not configuration files. Fire & forget (re-) installation is possible.
configure (): install and apply configuration. configure (): install and apply configuration.
} }
class Domain class Domain
@ -45,7 +45,22 @@ Application ..> Domain
package infrastructure { package infrastructure {
class Repository class Repository
class Provs class Provs {
create<type>(): create a new item - might also have a parameter like: skipIfExisting
delete<type>(): delete an item - might also have a parameter like: failIfNotExisting
check<type>(): check if an item exists (returns true resp. false)
check<type>Content(): check content of item (returns true resp. false), e.g. checkFileContent
check<type>Runs(): check if container/service is running (returns true resp. false)
start<type>(): start e.g. a container (or a service)
stop<type>(): stop a container/service
remove<type>(): remove e.g. a container or image
—————————————————————————————————————————————————————— ()
Remark1: types can be e.g.: "file", "dir", "user", "container" (depending on the command)
Remark2: References to external software (or modules) should generally follow the external naming conventions.
(E.g. for kubectl commands the verbs might include: apply, delete, get, describe, etc)
}
} }
Service ..> Domain Service ..> Domain
Service ..> Service Service ..> Service