Custom State Build

Custom State Release Package

The key construct for the Authoritative Release is that all aspects of the release process are predictable and repeatable. Configuration and helper scripts are packaged into an immutable release. No build process is required, so the minimal CDAF.solution is all that is required, assuming the custom state management is placed in the custom directory within the solution directory, e.g.

devops
├── CDAF.solution
├── custom
│   ├── anypoint.sh
│   ├── delta.sh
│   ├── promote.tsk
│   └── properties.varchk
├── app-components.cm
├── patient-summary-app.cm
└── properties.cm

Example of minimal CDAF.solution

solutionName=anypoint
productName=Mulesoft Anypoint Platform
artifactPrefix=0.7

The configuration files are transformed into properties files

The custom deployment tools are included due to being in the custom directory

And the release package is created