Comment 3 for bug 1923360

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tacker (master)

Reviewed: https://review.opendev.org/c/openstack/tacker/+/785798
Committed: https://opendev.org/openstack/tacker/commit/2c68a0a84d2a62598b9379529008c2ae1c849ca6
Submitter: "Zuul (22348)"
Branch: master

commit 2c68a0a84d2a62598b9379529008c2ae1c849ca6
Author: Sheel Rana <email address hidden>
Date: Sun Apr 4 22:26:47 2021 +0530

    Updated vnflcm api output with host-path

    Currently vnflcm api operations do not return host-path
    in their output inside '_links' href field.
    For ex,
    "_links": {
    "self": {
    "href":
        "/vnflcm/v1/vnf_instances/<vnf-instance>"
    }
    }

    This patch updates '_links' href field in vnflcm api output
    with host-path.
    For ex,
    "_links": {
    "self": {
    "href":
        "http://localhost:9890/vnflcm/v1/vnf_instances/<vnf-instance>"
    }
    }

    *here "http://localhost:9890/" is just an example of host-path.

    Related operations:
    1. Creates a new VNF instance.
    2. Show VNF Instance.
    3. List VNF Instances.
    4. Show VNF LCM operation occurrence.
    5. List VNF LCM operation occurrences.

    Co-Authored-By: Navum Gupta <email address hidden>

    Closes-Bug: #1923360
    Change-Id: I245cd2626fac1112d6a9fef3c51bf5ef6b679e05