Valence

[API] should allow compose node without properties

Bug #1701122 reported by Lin Yang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Valence
Fix Released
Undecided
Lin Yang

Bug Description

Current valence API require user to specify the "properties" field when compose node. This limitation is unnecessary, like podm allow user to compose node without any properties, but only the name.

https://github.com/openstack/valence/blob/577474c9c06d0fdb2c113627f8641ae3b6880e05/valence/validation/schemas.py#L31

Lin Yang (lin-a-yang)
Changed in openstack-valence:
assignee: nobody → Lin Yang (lin-a-yang)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to valence (master)

Fix proposed to branch: master
Review: https://review.openstack.org/478674

Changed in openstack-valence:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to valence (master)

Reviewed: https://review.openstack.org/478674
Committed: https://git.openstack.org/cgit/openstack/valence/commit/?id=4d5a93a2a1e3a419351e75ecb7f14b92ec5d6eb8
Submitter: Jenkins
Branch: master

commit 4d5a93a2a1e3a419351e75ecb7f14b92ec5d6eb8
Author: Lin Yang <email address hidden>
Date: Wed Jun 28 16:05:26 2017 -0700

    Allow compose node without properties

    Valence should allow user to compose node without properties, and
    let podm to assign one by default, but validation schema block it. So
    fix it in schema for node composition.

    Change-Id: I00e08aae3d33bbd37c0bac633345c09eb19342af
    Closes-Bug: #1701122

Changed in openstack-valence:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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