# AMP Release 5.6.0

* [Introduction](#introduction)
* [New Features](#new-features)
* [Bug Fixes](#bug-and-vulnerability-fixes)
* [Known Issues](#known-issues)
* [Backwards Compatibility](#backwards-compatibility)
* [Deprecation Announcements](#deprecation-announcements)
* [Installation and Upgrade Instructions](#installation-and-upgrade-instructions)


## Introduction

Thank you to our customers and users for their feedback and support.
Thanks also go to the Apache Brooklyn community for the many code contributions and
evolution of ideas at the heart of this product.

For more information, visit https://cloudsoft.io/software, https://docs.cloudsoft.io
and https://brooklyn.apache.org.


## New Features

* Arbitrary types can be defined as beans and referenced as config, sensors, etc
* Config constraint violations are detected earlier and more information on errors returned
* An additional post-init hook is available for custom Entity behaviour to run after initialization
* The Catalog UI and `/bundle/` REST API support downloading a ZIP of bundles in the catalog
* Deploying from the catalog will now populate the parameters from the catalog item
* When using WinRM with PowerShell, additional streams are created for improved display in the UI
* Various other improvements for Kubernetes, Terraform, VMWare, Windows, and more
* Hashicorp Vault support to latest version

## Bug and Vulnerability Fixes

* Several dependency versions have been updated to fix known vulnerabilities in upstream software.
  These do not make AMP vulnerable, but as good practice AMP is regularly upgraded to use upstream libraries without CVEs.
  Please see the following:
  * https://github.com/apache/brooklyn-server/pull/1140
  * https://github.com/cloudsoft/winrm4j/pull/134
  * https://github.com/cloudsoft/amp-cluster/pull/196
* In some cases, when applications are added in applications, they were not unwrapped, resulting in an additional layer in the runtime hierarchy.
  This has been fixed.
* Various other minor bugs have been resolved

## Known Issues

No known issues.

## Backwards Compatibility

* TOSCA 1.1 is not included by default pending the release of the new TOSCA 1.3 support planned for the next major release.
  Either version is available on request.

* ConfigKey constraints are now in some circumstances more tightly enforced, as noted above.
  This may cause issues when rebinding to persisted state that have ConfigKey values in violation of the constraints.

## Deprecation Announcements

No deprecation announcements.

## Installation and Upgrade Instructions

To install see https://docs.cloudsoft.io/operations/production-installation.html

To upgrade existing installations see https://docs.cloudsoft.io/operations/upgrades/