Abstract: Application artifact registration is performed by receiving a bundle service specification configured for deployment of a software service in a cloud native environment, transferring a bundle from an original address indicated in the bundle service specification to an object storage at a principal address, attaching, to the bundle service specification, a bundle identifier and the principal address, extracting a plurality of artifacts from the bundle, each of the plurality of artifacts being stored in the object storage at a subordinate address, and creating one or more artifact service specifications, each artifact service specification representing one or more of the plurality of artifacts, each service specification representing the corresponding subordinate address, an artifact identifier, and an artifact type of each represented artifact.

Abstract: Relationship-apparent application artifact registration is performed by attaching, to the bundle service specification, a bundle identifier, the principal address, and an artifact relationship specification, the artifact relationship specification representing, for each of the one or more artifact service specifications, the subordinate address, the artifact identifier, and the artifact type of each represented artifact, and attaching, to each of the one or more artifact service specifications, a bundle relationship specification, the bundle relationship specification representing the bundle identifier and the principal address.

Abstract: Application artifact registration is performed by receiving a bundle service specification configured for deployment of a software service in a cloud native environment, transferring a bundle from an original address indicated in the bundle service specification to an object storage at a principal address, attaching, to the bundle service specification, a bundle identifier and the principal address, extracting a plurality of artifacts from the bundle, each of the plurality of artifacts being stored in the object storage at a subordinate address, and creating one or more artifact service specifications, each artifact service specification representing one or more of the plurality of artifacts, each service specification representing the corresponding subordinate address, an artifact identifier, and an artifact type of each represented artifact.

Abstract: A method includes creating a first package of an application, registering the first package with an orchestrator and triggering deployment of the application on a set of target servers. In response to triggering deployment of the application, the orchestrator obtains client identification of security information for the application, deploys the application on the set of target servers, submits the configuration files to a configuration management tool for configuration, applies the configuration files to perform configuration of the application in the set of target servers, and triggers an observability framework (OBF) tool to start application monitoring in response to at least the orchestrator submitting the monitoring configurations to the OBF tool, and monitors the application in the set of target servers. The first package includes deployment files, security information, management configurations of the application, or monitoring configurations for the OBF tool.

Abstract: Relationship-apparent application artifact registration is performed by attaching, to the bundle service specification, a bundle identifier, the principal address, and an artifact relationship specification, the artifact relationship specification representing, for each of the one or more artifact service specifications, the subordinate address, the artifact identifier, and the artifact type of each represented artifact, and attaching, to each of the one or more artifact service specifications, a bundle relationship specification, the bundle relationship specification representing the bundle identifier and the principal address.

Abstract: A method includes creating a package of an application, registering the package with an orchestrator, triggering instantiation of the application in the orchestrator, generating initial configuration files for the instantiation of the application, changing an application state of the application to a planned state, changing the application state to a Keycloak state in response to obtaining client identification of the Keycloak information for the application, changing the application state to an instantiated state in response to deploying the application on the set of target servers, changing the application state to a configured state in response applying daily configuration files to perform daily configuration of the application in the set of target servers, and changing the application state to a monitored state in response to monitoring the application in the set of target servers by an observability framework tool.