Skip to content

0.10.0 M4 WIP #77

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
FabrizioMoggio merged 4 commits into from
Sep 16, 2025
Merged

0.10.0 M4 WIP #77

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
dcc7d2e
Inconsistences
FabrizioMoggio Sep 16, 2025
feaf624
zone inconsistencies
FabrizioMoggio Sep 16, 2025
6d00706
zone
FabrizioMoggio Sep 16, 2025
e03c9eb
409
FabrizioMoggio Sep 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions code/API_definitions/traffic-influence.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -606,6 +606,8 @@ paths:
$ref: "#/components/responses/Generic403"
"404":
$ref: '#/components/responses/Generic404'
"409":
$ref: "#/components/responses/Generic409"
"422":
$ref: "#/components/responses/Generic422"
"429":
Expand Down
2 changes: 1 addition & 1 deletion code/Test_definitions/traffic-influence-postTrafficInfluence.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ Feature: CAMARA Traffic Influence API, vwip - Operation postTrafficInfluence and
@TI_Resource_LCM_Optional_Parameters_Valid_CREATE
Scenario: Create Traffic Influence (TI) Resource with also optional parameters
Given the request body property with mandatory valid parameters ("$.apiConsumerId", "$.appId")
And any other optional parameters (e.g. "$.AppInstanceId", "$.zone" etc.)
And any other optional parameters (e.g. "$.appInstanceId", "$.edgeCloudZoneId" etc.)
And the request body is set to a valid request body
When the HTTP "POST" request is sent
Then it should be created a new TI Resource
Expand Down
4 changes: 2 additions & 2 deletions code/Test_definitions/traffic-influence-postTrafficInfluenceDevice.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ Feature: CAMARA Traffic Influence API, vwip - Operation postTrafficInfluenceDevi
@TI_Resource_LCM_Optional_Parameters_Valid_CREATE_2-legs
Scenario: Create Traffic Influence (TI) Resource with also optional parameters with 2 legs
Given the request body property with mandatory valid parameters ("$.apiConsumerId", "$.appId", "$.device")
And any other optional parameters (e.g. "$.AppInstanceId", "$.zone" etc.)
And any other optional parameters (e.g. "$.appInstanceId", "$.edgeCloudZoneId" etc.)
And the request body is set to a valid request body
When the HTTP "POST" request is sent
Then it should be created a new TI Resource
Expand All @@ -84,7 +84,7 @@ Feature: CAMARA Traffic Influence API, vwip - Operation postTrafficInfluenceDevi
@TI_Resource_LCM_Optional_Parameters_Valid_CREATE_3-legs
Scenario: Create Traffic Influence (TI) Resource with also optional parameters with 3 legs
Given the request body property with mandatory valid parameters ("$.apiConsumerId", "$.appId")
And any other optional parameters (e.g. "$.AppInstanceId", "$.zone" etc.) with the request body set to a valid request body
And any other optional parameters (e.g. "$.appInstanceId", "$.edgeCloudZoneId" etc.) with the request body set to a valid request body
And The header "Authorization" is set to a valid access token identifying a device
When the HTTP "POST" request is sent
Then it should be created a new TI Resource
Expand Down