1. TOSCA v1.3 Deprecated Features and Non-Backward-Compatible Changes
April 8, 2019

2. Copyright © 2019 Ubicity Corp.
Deprecation in TOSCA
“A feature marked as deprecated in a particular version will be removed in the subsequent version of the specification”
As defined in Section of TOSCA Simple Profile in YAML v1.3
This means that features deprecated in v1.3 continue to be fully supported, but will be removed in v2.0
Copyright © 2019 Ubicity Corp.

3. Features Deprecated in v1.3
Section
Feature
Description
3.4.3
Directives
“substitutable” and “selectable” directives have been deprecated. These directives have been replaced with “substitute” and “select” respectively.
Namespace URI
The namespace_uri keyword has been removed from import definitions. This URI must be assigned in the namespace definition itself.
3.6.20
Operation definitions
Operation definitions in Interface definitions must now use the operations keyword explicitly. Operation definitions without the operations keyword has been deprecated.
Event type
The event_type keyword in policy trigger definitions has been deprecated. It has been replaced with the event keyword.
Assertion definition
The assert clause in condition clauses has been deprecated, since it is logically equivalent to the and clause.
Copyright © 2019 Ubicity Corp.

4. Features Deprecated in v1.3 (cont’d)
Section
Feature
Description
3.7.11
Groups
Interface definitions, capability definitions, and requirement definitions have been removed from group type definitions and group definitions. Groups only exist for purposes of uniform application of policies to collections of nodes. Consequently, groups do not have a lifecycle of their own and must not have interfaces.
3.8.8
Property mappings
The “property-to-fixed-value” mapping has been removed from substitution_mapping syntax. This feature only existed to control selection of the appropriate substituting template when multiple candidates exist. It has been replaced with substitution_filter.
The “property-to-property” mapping has also been removed since it resulted in ambiguous and undefined behavior.
4.6.1
Operation output
The get_operation_output intrinsic function has been removed. It has been replaced with explicit “output-to-attribute” mappings in interface definitions.
Copyright © 2019 Ubicity Corp.

5. Non-Backward Compatible Changes in v1.3 (cont’d)
Section
Feature
Description
3.6.22
Trigger action
Trigger definitions include an action keyword that specifies the action triggered by an event when a given condition is satisfied).
In v1.2 of the specification, the action keyword defines a single interface operation or a single workflow.
In v1.3, the action keyword defines a list of activity definitions.
Because of this change, trigger definitions and workflow steps now both specify lists of activities, which results in a more consistent grammar.
Copyright © 2019 Ubicity Corp.