Difference between revisions of "PKC DevOps/Goal"
Jump to navigation
Jump to search
| (10 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
# | The foremost goal of the PKC DevOps practice is to ensure [[composability]] in all three levels, [[Data Content]], in [[Collaborative Workflow]], and in [[Deployment Infrastructure]]s. | ||
#At every stage, make sure all the software or hardware requirements are met, and tries to install or instruct the user to do the right thing using [[IaC]] tools. | |||
#Lower the entry-barrier for digitized [[value production]] and [[value exchange|exchange]] workflow. | |||
#Allow for a secure and user-friendly [[Pull Request]] for all kinds of [[DevOps workflows]]. | |||
#Create a [[PKC namespace]] that is [[sound, precise, and terminable]] by each development cycle. | #Create a [[PKC namespace]] that is [[sound, precise, and terminable]] by each development cycle. | ||
<noinclude> | <noinclude> | ||
==Related Pages== | ==Related Pages== | ||
*[[has LogicModel:: | *[[has LogicModel::PKC DevOps]] | ||
</noinclude> | </noinclude> | ||
Latest revision as of 13:43, 14 August 2021
The foremost goal of the PKC DevOps practice is to ensure composability in all three levels, Data Content, in Collaborative Workflow, and in Deployment Infrastructures.
- At every stage, make sure all the software or hardware requirements are met, and tries to install or instruct the user to do the right thing using IaC tools.
- Lower the entry-barrier for digitized value production and exchange workflow.
- Allow for a secure and user-friendly Pull Request for all kinds of DevOps workflows.
- Create a PKC namespace that is sound, precise, and terminable by each development cycle.