From 1bd03de6cced808bff05bf4d2b13e5a0866730f0 Mon Sep 17 00:00:00 2001 From: XunliYang Date: Wed, 10 Dec 2025 11:19:34 +0800 Subject: [PATCH] reset API version in main branch to wip --- code/API_definitions/network-slice-assignment.yaml | 2 +- code/API_definitions/network-slice-booking.yaml | 4 ++-- .../network-slice-assignment-assign.feature | 6 +++--- code/Test_definitions/network-slice-assignment-get.feature | 6 +++--- .../network-slice-assignment-release.feature | 6 +++--- .../network-slice-assignment-retrieve.feature | 6 +++--- .../network-slice-booking-createSession.feature | 6 +++--- .../network-slice-booking-deleteSession.feature | 6 +++--- .../network-slice-booking-getSession.feature | 6 +++--- 9 files changed, 24 insertions(+), 24 deletions(-) diff --git a/code/API_definitions/network-slice-assignment.yaml b/code/API_definitions/network-slice-assignment.yaml index eecb376..961ac0c 100644 --- a/code/API_definitions/network-slice-assignment.yaml +++ b/code/API_definitions/network-slice-assignment.yaml @@ -48,7 +48,7 @@ info: As a specific rule, error `501 - NOT_IMPLEMENTED` can be only a possible error response if it is explicitly documented in the API. - version: 0.1.0 + version: wip x-camara-commonalities: 0.6 license: name: Apache 2.0 diff --git a/code/API_definitions/network-slice-booking.yaml b/code/API_definitions/network-slice-booking.yaml index d0a5b82..380b5e3 100644 --- a/code/API_definitions/network-slice-booking.yaml +++ b/code/API_definitions/network-slice-booking.yaml @@ -43,7 +43,7 @@ info: As a specific rule, error `501 - NOT_IMPLEMENTED` can be only a possible error response if it is explicitly documented in the API. - version: 0.1.0 + version: wip x-camara-commonalities: 0.6 license: name: Apache 2.0 @@ -52,7 +52,7 @@ externalDocs: description: Project documentation at CAMARA url: https://github.com/camaraproject/NetworkSliceBooking servers: - - url: "{apiRoot}/network-slice-booking/v0.1" + - url: "{apiRoot}/network-slice-booking/vwip" variables: apiRoot: default: http://localhost:9100 diff --git a/code/Test_definitions/network-slice-assignment-assign.feature b/code/Test_definitions/network-slice-assignment-assign.feature index a31163f..905414c 100644 --- a/code/Test_definitions/network-slice-assignment-assign.feature +++ b/code/Test_definitions/network-slice-assignment-assign.feature @@ -1,4 +1,4 @@ -Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation assign +Feature: CAMARA Network Slice Assignment API vwip - Operation assign # Input to be provided by the implementation to the tester # @@ -7,11 +7,11 @@ Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation assign # * List of device identifier types which are not supported, among: phoneNumber, ipv4Address, ipv6Address. # * For this version, CAMARA does not allow the use of networkAccessIdentifier, so it is considered by default as not supported. # - # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version 0.1.0 + # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version wip Background: Common assignSlice setup Given an environment at "apiRoot" - And the resource "/network-slice-assignment/v0.1/slices/devices/assign" + And the resource "/network-slice-assignment/vwip/slices/devices/assign" And the header "Content-Type" is set to "application/json" And the header "Authorization" is set to a valid access token And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator" diff --git a/code/Test_definitions/network-slice-assignment-get.feature b/code/Test_definitions/network-slice-assignment-get.feature index 7d91c9c..8f2f318 100644 --- a/code/Test_definitions/network-slice-assignment-get.feature +++ b/code/Test_definitions/network-slice-assignment-get.feature @@ -1,4 +1,4 @@ -Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation get +Feature: CAMARA Network Slice Assignment API vwip - Operation get # Get information about devices assigned to an existing network slice. @@ -14,11 +14,11 @@ Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation get # * List of device identifier types which are not supported, among: phoneNumber, ipv4Address, ipv6Address. # * For this version, CAMARA does not allow the use of networkAccessIdentifier, so it is considered by default as not supported. # - # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version 0.1.0 + # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version wip Background: Common getDevice setup Given an environment at "apiRoot" - And the resource "/network-slice-assignment/v0.1/slices/devices/get/{sliceId}" + And the resource "/network-slice-assignment/vwip/slices/devices/get/{sliceId}" And the header "Content-Type" is set to "application/json" And the header "Authorization" is set to a valid access token And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator" diff --git a/code/Test_definitions/network-slice-assignment-release.feature b/code/Test_definitions/network-slice-assignment-release.feature index 6fb50cf..d30f6a1 100644 --- a/code/Test_definitions/network-slice-assignment-release.feature +++ b/code/Test_definitions/network-slice-assignment-release.feature @@ -1,4 +1,4 @@ -Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation release +Feature: CAMARA Network Slice Assignment API vwip - Operation release # Input to be provided by the implementation to the tester # @@ -9,11 +9,11 @@ Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation release # * The AssignmentInfo of an existing Slice assignment # * The AssignmentInfo of an existing Slice assignment with status "AVAILABLE", and with provided values for "sink" and "sinkCredential" # - # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version 0.1.0 + # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version wip Background: Common releaseSlice setup Given an environment at "apiRoot" - And the resource "/network-slice-assignment/v0.1/slices/devices/release" + And the resource "/network-slice-assignment/vwip/slices/devices/release" And the header "Content-Type" is set to "application/json" And the header "Authorization" is set to a valid access token And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator" diff --git a/code/Test_definitions/network-slice-assignment-retrieve.feature b/code/Test_definitions/network-slice-assignment-retrieve.feature index bd14801..a0750bd 100644 --- a/code/Test_definitions/network-slice-assignment-retrieve.feature +++ b/code/Test_definitions/network-slice-assignment-retrieve.feature @@ -1,4 +1,4 @@ -Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation retrieve +Feature: CAMARA Network Slice Assignment API vwip - Operation retrieve # Retrieve the list of network slices to which a device is assigned. @@ -14,11 +14,11 @@ Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation retrieve # * List of device identifier types which are not supported, among: phoneNumber, ipv4Address, ipv6Address. # * For this version, CAMARA does not allow the use of networkAccessIdentifier, so it is considered by default as not supported. # - # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version 0.1.0 + # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version wip Background: Common retrieveSlice setup Given an environment at "apiRoot" - And the resource "/network-slice-assignment/v0.1/slices/devices/retrieve" + And the resource "/network-slice-assignment/vwip/slices/devices/retrieve" And the header "Content-Type" is set to "application/json" And the header "Authorization" is set to a valid access token And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator" diff --git a/code/Test_definitions/network-slice-booking-createSession.feature b/code/Test_definitions/network-slice-booking-createSession.feature index b6ed2b8..066efa2 100644 --- a/code/Test_definitions/network-slice-booking-createSession.feature +++ b/code/Test_definitions/network-slice-booking-createSession.feature @@ -1,4 +1,4 @@ -Feature: CAMARA Network Slice Booking API v0.1.0 - Operation createSlice +Feature: CAMARA Network Slice Booking API vwip - Operation createSlice # Input to be provided by the implementation to the tester # @@ -14,11 +14,11 @@ Feature: CAMARA Network Slice Booking API v0.1.0 - Operation createSlice # * An Area outside the supported area # * A combination of request parameters including service area, start time, and end time, configuration information of network slicing # - # References to OAS spec schemas refer to schemas specified in network-slice-booking.yaml, version 0.1.0 + # References to OAS spec schemas refer to schemas specified in network-slice-booking.yaml, version wip Background: Common createSlice setup Given an environment at "apiRoot" - And the resource "/network-slice-booking/v0.1/slices" + And the resource "/network-slice-booking/vwip/slices" And the header "Content-Type" is set to "application/json" And the header "Authorization" is set to a valid access token And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator" diff --git a/code/Test_definitions/network-slice-booking-deleteSession.feature b/code/Test_definitions/network-slice-booking-deleteSession.feature index cfc3f50..6ea2fc5 100644 --- a/code/Test_definitions/network-slice-booking-deleteSession.feature +++ b/code/Test_definitions/network-slice-booking-deleteSession.feature @@ -1,4 +1,4 @@ -Feature: CAMARA Network Slice Booking API v0.1.0 - Operation deleteSlice +Feature: CAMARA Network Slice Booking API vwip - Operation deleteSlice # Input to be provided by the implementation to the tester # @@ -7,11 +7,11 @@ Feature: CAMARA Network Slice Booking API v0.1.0 - Operation deleteSlice # # Testing assets: # * The sliceId of an existing slice. - # * References to OAS spec schemas refer to schemas specified in network-slice-booking.yaml, version 0.1.0 + # * References to OAS spec schemas refer to schemas specified in network-slice-booking.yaml, version wip Background: Common deleteSlice setup Given an environment at "apiRoot" - And the resource "/network-slice-booking/v0.1/slices/{sliceId}" + And the resource "/network-slice-booking/vwip/slices/{sliceId}" And the header "Content-Type" is set to "application/json" And the header "Authorization" is set to a valid access token And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator" diff --git a/code/Test_definitions/network-slice-booking-getSession.feature b/code/Test_definitions/network-slice-booking-getSession.feature index c068ab6..8605ed9 100644 --- a/code/Test_definitions/network-slice-booking-getSession.feature +++ b/code/Test_definitions/network-slice-booking-getSession.feature @@ -1,4 +1,4 @@ -Feature: CAMARA Network Slice Booking API v0.1.0 - Operation getSlice +Feature: CAMARA Network Slice Booking API vwip - Operation getSlice # Input to be provided by the implementation to the tester # @@ -7,11 +7,11 @@ Feature: CAMARA Network Slice Booking API v0.1.0 - Operation getSlice # # Testing assets: # * The sliceId of an existing slice. - # * References to OAS spec schemas refer to schemas specified in network-slice-booking.yaml, version 0.1.0 + # * References to OAS spec schemas refer to schemas specified in network-slice-booking.yaml, version wip Background: Common getSlice setup Given an environment at "apiRoot" - And the resource "/network-slice-booking/v0.1/slices/{sliceId}" + And the resource "/network-slice-booking/vwip/slices/{sliceId}" And the header "Content-Type" is set to "application/json" And the header "Authorization" is set to a valid access token And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator"