Compatibility and Versioning
This topic describes Platform Automation Toolkit dependencies and semantic versioning.
Platform Automation Toolkit is designed to work with these dependencies.
|Platform Automation Toolkit||Concourse||Ops Manager||Pivnet Resource|
credhub-interpolate in Concourse 5.x+ only.
If using Concourse 4.x, continue using
If using Concourse 5.x+, it is strongly recommended to switch to
For more information about secrets handling, reference the Secrets Handling Page.
Ops Manager 2.5
The filename for the artifact downloaded from Ops Manager is changed! If your resources or pipelines have a regex for the Ops Manager filename, you may be affected. (Please see Ops Manager's official notice for more information)
This product uses semantic versioning 2.0.0 to describe the impact of changes to our concourse tasks. In order to take advantage of semantic versioning, we must declare an API.
The following are considered part of our API:
Our concourse tasks':
- inputs and outputs (including the format/required information in config files)
- specified parameters
- intended and specified functionality
These are all documented for each task within the task files themselves.
The minimum compatible version of Concourse and Ops Manager are part of the API, and are specified here.
The presence of the following binaries on the combined image:
The patterns necessary to specify our files on Tanzu Network: We will consider it a breaking change if any of the following glob patterns for the Platform Automation Toolkit image and tasks fail to return a single match when used with the
platform-automation-image-*.tgz# all IaaSes image
vsphere-platform-automation-image-*.tar.gz# vSphere only image
The following are NOT covered:
omcommand line tool
p-automatorcommand line tool
- the dependencies on the image intended to be used with our tasks
- non-specified parameters (for instance, any env var used by a CLI we call but not specified as a parameter on the task)
- properties specific to particular product or ops manager versions in config files (which are governed by the product being configured, not our tooling)
- Versions of the included binaries. The presence of those binaries are guaranteed, but the versions are not.
In general, if we make any change that we anticipate could not be consumed without manual changes, we consider it a breaking change, and increment the major version accordingly.
This assumes that the required image can be made automatically available; each version of our tasks is designed for and tested with only the version of the image that shipped with it.
If we accidentally violate our semver, we will publish an additional version addressing the problem. In some cases, that may mean releasing the same software with a corrected version, and shipping a new patch version identical to the version prior to the violation. In others, it may mean releasing an additional patch version which reverts an unintentional breaking change.
This should make it safe to automatically consume our release. Patch releases should be very safe to automatically update to. Minor versions should be safe, but it can be more difficult to anticipate the effect of new features, so this is slightly riskier. Major versions should be expected to break for at least some users when consumed automatically. Automatic consumption of major versions should be limited to test/staging environments intended to endure and detect such breakage.