internal tosca definitions overwrite custom definitions

Bug #1883562 reported by Валерия Валерьевна Швецова
This bug affects 1 person
Affects Status Importance Assigned to Milestone
TOSCA Parser

Bug Description

The user can't make any changes in OpenStack TOSCA definition, for example of tosca.nodes.Compute type.

The template example isn't working, but is expected to be successfully validated

tosca_definitions_version: tosca_simple_yaml_1_0

    description: > <...>
    derived_from: tosca.capabilities.Root
        type: string
        required: true
        default: tcp
        type: string
        required: false

      type: tosca.nodes.Compute
            protocol: tcp
            port: "{{ port }}"
            initiator: target

information type: Public → Public Security
information type: Public Security → Public
Revision history for this message
Валерия Валерьевна Швецова (versus-vv) wrote :

Yasufumi Ogawa, I have proposed some changes for this bug ( and wait for reviewer.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tosca-parser 2.4.0

This issue was fixed in the openstack/tosca-parser 2.4.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.