tripleo-heat-templates/releasenotes/notes/disable-heat-api-cloudwatch-d5a471da22472bde.yaml
marios 4d21451666 Remove Heat Cloudwatch API during upgrade and disable by default
This adds a heat-api-cloudwatch-disabled.yaml and wires it up in
the resource registry. During the Ocata to Pike upgrade this service
will thus be stopped and disabled by default.

If you wish to keep the Heat Cloudwatch API then you should instead
use the provided heat-api-cloudwatch.yaml environment file.

Change-Id: I3f90a9799b90ca365f675f593371c1d3701fede6
Related-Bug: 1713531
2017-10-10 12:53:03 +03:00

16 lines
672 B
YAML

---
upgrade:
- |
The Heat API Cloudwatch API is deprecated in Pike and so it removed
by default during the Ocata to Pike upgrade. If you wish to keep this
service then you should use the environments/heat-api-cloudwatch.yaml
environment file in the tripleo-heat-templates during the upgrade (note
that this is migrated to running under httpd, if you do decide to keep
this service on Pike).
deprecations:
- |
The Heat API Cloudwatch API is deprecated in Pike and so it is now not
deployed by default. You can override this behaviour with the
environments/heat-api-cloudwatch.yaml environment file in the
tripleo-heat-templates.