Abstract: Concepts for synchronising and maintaining audited code and toolchain access in a modern software development pipeline are presented. In particular, by leveraging software bots (also known as software development bots) to monitor changes in a development team's preferred access control mechanism, such changes in the preferred state can be stored as preferred/target configuration in a source controlled repository. Further, the same (or other) software bots may be used to monitor for configuration drift between the source-controlled system and the preferred/target configuration stored in the repository and eliminate drifts automatically if possible or alert interested parties about those drifts.

Abstract: Concepts for synchronising and maintaining audited code and toolchain access in a modern software development pipeline are presented. In particular, by leveraging software bots (also known as software development bots) to monitor changes in a development team's preferred access control mechanism, such changes in the preferred state can be stored as preferred/target configuration in a source controlled repository. Further, the same (or other) software bots may be used to monitor for configuration drift between the source-controlled system and the preferred/target configuration stored in the repository and eliminate drifts automatically if possible or alert interested parties about those drifts.

Abstract: Provided are techniques for securely processing secret values in application configurations. A configuration file for an application is retrieved from a first repository, where the configuration file stores a configuration value and a link to a secret value in a second repository. The secret value is retrieved from the second repository using the link. The configuration value is hashed to output a hashed configuration value and the secret value is hashed to output a hashed secret value. The hashed configuration value is signed, with a private key, to output a hashed and signed configuration value, and the hashed secret value is signed, with the private key, to output a hashed and signed secret value. The configuration value, the secret value, the hashed and signed configuration value, and the hashed and signed secret value are stored in a release file. The application is executed using the release file.

Abstract: Provided are techniques for securely processing secret values in application configurations. A configuration file for an application is retrieved from a first repository, where the configuration file stores a configuration value and a link to a secret value in a second repository. The secret value is retrieved from the second repository using the link. The configuration value is hashed to output a hashed configuration value and the secret value is hashed to output a hashed secret value. The hashed configuration value is signed, with a private key, to output a hashed and signed configuration value, and the hashed secret value is signed, with the private key, to output a hashed and signed secret value. The configuration value, the secret value, the hashed and signed configuration value, and the hashed and signed secret value are stored in a release file. The application is executed using the release file.

Abstract: Disclosed embodiments provide techniques for automatic interdependency resolution for micro-service deployments. A micro-service deployment broker executing on a computing device obtains current environment and feature support of a deployed distributed computing environment. The micro-service deployment broker determines environment and feature requirements for a requested deployment, and compares that with the current environment and feature support of the deployed distributed computing environment. Based on the comparison, a deployment command is issued indicating the deployment plan for the requested deployment. In cases where deployment is not possible or only a partial deployment is possible, an indication is sent to an operator to indicate that full deployment did not occur.

Abstract: Disclosed embodiments provide techniques for automatic interdependency resolution for micro-service deployments. A micro-service deployment broker executing on a computing device obtains current environment and feature support of a deployed distributed computing environment. The micro-service deployment broker determines environment and feature requirements for a requested deployment, and compares that with the current environment and feature support of the deployed distributed computing environment. Based on the comparison, a deployment command is issued indicating the deployment plan for the requested deployment. In cases where deployment is not possible or only a partial deployment is possible, an indication is sent to an operator to indicate that full deployment did not occur.

Abstract: Disclosed embodiments provide techniques for automatic interdependency resolution for micro-service deployments. A micro-service deployment broker executing on a computing device obtains current environment and feature support of a deployed distributed computing environment. The micro-service deployment broker determines environment and feature requirements for a requested deployment, and compares that with the current environment and feature support of the deployed distributed computing environment. Based on the comparison, a deployment command is issued indicating the deployment plan for the requested deployment. In cases where deployment is not possible or only a partial deployment is possible, an indication is sent to an operator to indicate that full deployment did not occur.

Abstract: Disclosed embodiments provide techniques for automatic interdependency resolution for micro-service deployments. A micro-service deployment broker executing on a computing device obtains current environment and feature support of a deployed distributed computing environment. The micro-service deployment broker determines environment and feature requirements for a requested deployment, and compares that with the current environment and feature support of the deployed distributed computing environment. Based on the comparison, a deployment command is issued indicating the deployment plan for the requested deployment. In cases where deployment is not possible or only a partial deployment is possible, an indication is sent to an operator to indicate that full deployment did not occur.