From 78fb3c42ca40e987e531f5b6ff6feca008d55e29 Mon Sep 17 00:00:00 2001 From: Zane Bitter Date: Wed, 27 Sep 2017 10:11:48 -0400 Subject: [PATCH] Add release note for StackDefinition API Change-Id: I00f71f9b47690d9e9fcbd8aeae2289de34d87c60 Implements: blueprint stack-definition --- ...tack-definition-in-functions-3f7f172a53edf535.yaml | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 releasenotes/notes/stack-definition-in-functions-3f7f172a53edf535.yaml diff --git a/releasenotes/notes/stack-definition-in-functions-3f7f172a53edf535.yaml b/releasenotes/notes/stack-definition-in-functions-3f7f172a53edf535.yaml new file mode 100644 index 0000000000..4db2c3e067 --- /dev/null +++ b/releasenotes/notes/stack-definition-in-functions-3f7f172a53edf535.yaml @@ -0,0 +1,11 @@ +--- +other: + - Intrinsic function plugins will now be passed a StackDefinition object + instead of a Stack object. When accessing resources, the StackDefinition + will return ResourceProxy objects instead of Resource objects. These + classes replicate the parts of the Stack and Resource APIs that are used by + the built-in Function plugins, but authors of custom third-party + Template/Function plugins should audit them to ensure they do not depend on + unstable parts of the API that are no longer accessible. The + StackDefinition and ResourceProxy APIs are considered stable and any future + changes to them will go through the standard deprecation process.