Content-Type of the v1 modify vnflcm request is not "application/merge-patch+json"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tacker |
In Progress
|
Undecided
|
Takahiro Miyajima |
Bug Description
Content-Type of the v1 modify vnflcm request is not "application/
As the same, Content-Type of all patch request is not "application/
All patch requests:
- PATCH VNF LCM(V1) cf.SOL003(v2.6.1) 5.4.3.3.4 PATCH
- PATCH VNF packages cf.SOL005(v3.3.1) 9.4.3.3.4 PATCH
- PATCH VNF LCM(V2) cf.SOL003(v3.3.1) 5.4.3.3.4 PATCH
- PATCH VNF FM cf.SOL003(v3.3.1) 7.4.3.3.4 PATCH
- PATCH VNF PM(Modify a PM job) cf.SOL003(v3.3.1) 6.4.3.3.4 PATCH
- PATCH VNF PM(Modify a PM threshold) cf.SOL003(v3.3.1) 6.4.6.3.4 PATCH
And, in the existing implementation, Accept of all patch request and put vnfpkgm request will be equal to Content-Type.
Accept of these request should be "application/json".
Changed in tacker: | |
assignee: | nobody → Takahiro Miyajima (f-miyajima) |
status: | New → In Progress |
Hi,
I'd like to request some clarification regarding this bug report description.
1. Please confirm the specific SOL003 version used as a reference for this bug report. Is it 2.6.1 or another version?
2. Are the proposed changes specific to VNFLCM and VNF package v1, or are modifications required for v2 as well?
3. As per SOL003 and SOL005 specification, changes are required in SOL005 as well for updloading and modification of vnf package
but bug description mentions changes for SOL003 operations only. Why?
To ensure a clear understanding, could you please consider adding more details to the bug description like what are the proposed changes to resolve this gap and where in the codebase will these changes be implemented?