From 3bac4abbda487347964bbadc4315b0693fd961b0 Mon Sep 17 00:00:00 2001
From: Monty Taylor <mordred@inaugust.com>
Date: Thu, 6 Jun 2019 09:39:34 -0500
Subject: [PATCH] Add release note for new disable service functionality

The behavior of disabling a service has changed slightly.

Change-Id: If7ee3aed6696308d15932c31f2ffb14486b30889
---
 .../notes/disable-service-39df96ef8a817785.yaml      | 12 ++++++++++++
 1 file changed, 12 insertions(+)
 create mode 100644 releasenotes/notes/disable-service-39df96ef8a817785.yaml

diff --git a/releasenotes/notes/disable-service-39df96ef8a817785.yaml b/releasenotes/notes/disable-service-39df96ef8a817785.yaml
new file mode 100644
index 000000000..aab0d5824
--- /dev/null
+++ b/releasenotes/notes/disable-service-39df96ef8a817785.yaml
@@ -0,0 +1,12 @@
+---
+features:
+  - |
+    ``has_{service_type}`` is a boolean config option that allows
+    asserting that a given service does not exist or should not be used
+    in a given cloud. Doing this will now cause the corresponding
+    service ``Proxy`` object to not be created and in its place is
+    an object that will throw exceptions if used.
+  - |
+    ``{service_type}_disabled_reason`` is a new string config option
+    that can be set to indicate a reason why a service has been disabled.
+    This string will be used in exceptions or log warnings emitted.