From ca81b07ef2ba41840e1d6c8e0e20fc7130fb2b37 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Fri, 29 Aug 2025 22:16:45 +0100 Subject: [PATCH 01/28] Update CHANGELOG.md --- CHANGELOG.md | 62 +++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 61 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index c59f5b2..389b45f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,7 +2,8 @@ ## Table of contents -- **[r1.1](#r11)** +- **[r1.2](#r12) (Fall25 public release)** +- [r1.1](#r11) **Please be aware that the project will have frequent updates to the main branch. There are no compatibility guarantees associated with code in any branch, including main, until it has been released. For example, changes may be reverted before a release is published. For the best results, use the latest published release.** @@ -13,6 +14,65 @@ The below sections record the changes for each API version in each release as fo * for subsequent release-candidate(s), only the delta to the previous release-candidate * for a public release, the consolidated changes since the previous public release +# r1.2 + +## Release Notes + +This release contains the definition and documentation of +* qos-booking v0.1.0 +* qos-booking-and-assignment v0.1.0 + +The API definition(s) are based on +* Commonalities v0.6.0 (r3.3) +* Identity and Consent Management v0.4.0 (r3.3) + +## qos-booking v0.1.0 + +**qos-booking v0.1.0 is the first initial release of this new API.** + +- API definition **with inline documentation**: + - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/QoSBooking/r1.2/code/API_definitions/qos-booking.yaml&nocors) + - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/QoSBooking/r1.2/code/API_definitions/qos-booking.yaml) + - OpenAPI [YAML spec file](https://github.com/camaraproject/QoSBooking/blob/r1.2/code/API_definitions/qos-booking.yaml) + +### Added +* N/A + +### Changed +* N/A + +### Fixed +* Align qos-booking with Commonalities r3.3 by @jlurien in [#40](https://github.com/camaraproject/QoSBooking/pull/40) +* Fix files of qos-booking for compliance with centralised linting rules by @Masa8106 in [#41](https://github.com/camaraproject/QoSBooking/pull/41) + +### Removed +* N/A + +## qos-booking-and-assignment v0.1.0 + +**qos-booking-and-assignment v0.1.0 is the first initial release of this new API.** + +- API definition **with inline documentation**: + - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/QoSBooking/r1.2/code/API_definitions/qos-booking-and-assignment.yaml&nocors) + - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/QoSBooking/r1.2/code/API_definitions/qos-booking-and-assignment.yaml) + - OpenAPI [YAML spec file](https://github.com/camaraproject/QoSBooking/blob/r1.2/code/API_definitions/qos-booking-and-assignment.yaml) + +### Added +* Added examples to address the issue #33 by @RamTMO in [#35](https://github.com/camaraproject/QoSBooking/pull/35) + +### Changed +* N/A + +### Fixed +* Fix DeviceResponse Issue #30 in QoS Booking and Assignment by @RmaTMO in [#34](https://github.com/camaraproject/QoSBooking/pull/34) +* Align qos-booking with Commonalities r3.3 by @jlurien in [#40](https://github.com/camaraproject/QoSBooking/pull/40) +* Update qos-booking-and-assignment.yaml to support issues by @RmaTMO in [#43](https://github.com/camaraproject/QoSBooking/pull/43) +* Fix DeviceCount related issues by @RmaTMO in [#48](https://github.com/camaraproject/QoSBooking/pull/48) +* bookingId related issues & remaining linting issues by @RmaTMO in [#50](https://github.com/camaraproject/QoSBooking/pull/50) + +### Removed +* Remove unnecessary spaces, tabs, lfs in qos-booking-and-assignment.feature file by @RmaTMO in #44 + # r1.1 ## Release Notes From 7de622bc659ec9764c6be35118b443a4468c4b0f Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Fri, 29 Aug 2025 22:29:40 +0100 Subject: [PATCH 02/28] Update README.md --- README.md | 15 +++------------ 1 file changed, 3 insertions(+), 12 deletions(-) diff --git a/README.md b/README.md index e6a9fa3..4de8149 100644 --- a/README.md +++ b/README.md @@ -25,21 +25,12 @@ Sandbox API Repository to describe, develop, document, and test the QoSBooking S ## Release Information -The repository has no releases yet, work in progress is within the main branch. - - - - - - * Note: Please be aware that the project will have updates to the main branch. There are no compatibility guarantees associated with code in any branch, including main, until a new release is created. For example, changes may be reverted before a release is created. For best results, use the latest available release. -* **The first pre-release of CAMARA QoS Booking is [r1.1](https://github.com/camaraproject/QoSBooking/releases/tag/r1.1)**. The Release Tag is [r1.1](https://github.com/camaraproject/QoSBooking/releases/tag/r1.1). - - - Contains the following API definitions **with inline documentation**: +* **NEW**: **The latest public release is [r1.2](https://github.com/camaraproject/QoSBooking/releases/tag/r1.2), with the following API versions:** - - qos-booking 0.1.0-rc.1 (booking QoS for a single device for a certain time and area)
[YAML spec file](https://github.com/camaraproject/QoSBooking/blob/r1.1/code/API_definitions/qos-booking.yaml) | [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/QoSBooking/r1.1/code/API_definitions/qos-booking.yaml&nocors) | [View it on Swagger Editor](https://camaraproject.github.io/swagger-ui/?url=https://raw.githubusercontent.com/camaraproject/QoSBooking/r1.1/code/API_definitions/qos-booking.yaml&nocors) - - qos-booking-and-assignment 0.1.0-rc.1 (booking QoS for multiple devices for a certain time and area, and assignment of devices to the booking, e.g. on a later time)
[YAML spec file](https://github.com/camaraproject/QoSBooking/blob/r1.1/code/API_definitions/qos-booking-and-assignment.yaml) | [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/QoSBooking/r1.1/code/API_definitions/qos-booking-and-assignment.yaml&nocors) | [View it on Swagger Editor](https://camaraproject.github.io/swagger-ui/?url=https://raw.githubusercontent.com/camaraproject/QoSBooking/r1.1/code/API_definitions/qos-booking-and-assignment.yaml&nocors) + - qos-booking 0.1.0 (booking QoS for a single device for a certain time and area)
[YAML spec file](https://github.com/camaraproject/QoSBooking/blob/r1.2/code/API_definitions/qos-booking.yaml) | [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/QoSBooking/r1.2/code/API_definitions/qos-booking.yaml&nocors) | [View it on Swagger Editor](https://camaraproject.github.io/swagger-ui/?url=https://raw.githubusercontent.com/camaraproject/QoSBooking/r1.2/code/API_definitions/qos-booking.yaml&nocors) + - qos-booking-and-assignment 0.1.0 (booking QoS for multiple devices for a certain time and area, and assignment of devices to the booking, e.g. on a later time)
[YAML spec file](https://github.com/camaraproject/QoSBooking/blob/r1.2/code/API_definitions/qos-booking-and-assignment.yaml) | [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/QoSBooking/r1.2/code/API_definitions/qos-booking-and-assignment.yaml&nocors) | [View it on Swagger Editor](https://camaraproject.github.io/swagger-ui/?url=https://raw.githubusercontent.com/camaraproject/QoSBooking/r1.2/code/API_definitions/qos-booking-and-assignment.yaml&nocors) ## Contributing * Meetings are held virtually From 3de79aae467d593837d89ea9ae9492854708aeda Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Fri, 29 Aug 2025 23:43:32 +0100 Subject: [PATCH 03/28] Update qos-booking-and-assignment.yaml --- code/API_definitions/qos-booking-and-assignment.yaml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/code/API_definitions/qos-booking-and-assignment.yaml b/code/API_definitions/qos-booking-and-assignment.yaml index 16f213d..c9517eb 100644 --- a/code/API_definitions/qos-booking-and-assignment.yaml +++ b/code/API_definitions/qos-booking-and-assignment.yaml @@ -77,7 +77,7 @@ info: license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html - version: wip + version: 0.1.0 x-camara-commonalities: 0.6 externalDocs: @@ -85,7 +85,7 @@ externalDocs: url: https://github.com/camaraproject/QoSBooking servers: - - url: "{apiRoot}/qos-booking-and-assignment/vwip" + - url: "{apiRoot}/qos-booking-and-assignment/v0.1" variables: apiRoot: default: http://localhost:9091 @@ -2038,3 +2038,4 @@ components: summary: No bookings found for the device description: No bookings are found for the device, value contains only empty array value: [] + From 1732b9fb703a63f34bde5e3ea30bc0ee823bb8a1 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Fri, 29 Aug 2025 23:44:35 +0100 Subject: [PATCH 04/28] Update qos-booking.yaml --- code/API_definitions/qos-booking.yaml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/code/API_definitions/qos-booking.yaml b/code/API_definitions/qos-booking.yaml index 2b3c3d8..0db08f8 100644 --- a/code/API_definitions/qos-booking.yaml +++ b/code/API_definitions/qos-booking.yaml @@ -69,7 +69,7 @@ info: license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html - version: wip + version: 0.1.0 x-camara-commonalities: 0.6 externalDocs: @@ -77,7 +77,7 @@ externalDocs: url: https://github.com/camaraproject/QoSBooking servers: - - url: "{apiRoot}/qos-booking/vwip" + - url: "{apiRoot}/qos-booking/v0.1" variables: apiRoot: default: http://localhost:9091 @@ -1486,3 +1486,4 @@ components: summary: No bookings found for the device description: An empty array is returned when no bookings are found for the device value: [] + From 5bca89d0d72e85512c32fd0a5fbf0bcc9da93ed6 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Fri, 29 Aug 2025 23:45:52 +0100 Subject: [PATCH 05/28] Delete code/Test_definitions/README.md --- code/Test_definitions/README.md | 1 - 1 file changed, 1 deletion(-) delete mode 100644 code/Test_definitions/README.md diff --git a/code/Test_definitions/README.md b/code/Test_definitions/README.md deleted file mode 100644 index 27a1f06..0000000 --- a/code/Test_definitions/README.md +++ /dev/null @@ -1 +0,0 @@ -This directory contains at least one `.feature` file containing test definitions for the repository API(s). From 5bf327522a72533360ea4c5272f4dcbde133fc35 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Fri, 29 Aug 2025 23:48:45 +0100 Subject: [PATCH 06/28] Update qos-booking-and-assignment.feature --- .../qos-booking-and-assignment.feature | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/code/Test_definitions/qos-booking-and-assignment.feature b/code/Test_definitions/qos-booking-and-assignment.feature index 6c292d0..9bb8726 100644 --- a/code/Test_definitions/qos-booking-and-assignment.feature +++ b/code/Test_definitions/qos-booking-and-assignment.feature @@ -1,4 +1,4 @@ -Feature: CAMARA QoS Booking and Assignment, vwip +Feature: CAMARA QoS Booking and Assignment, v0.1.0 # Input to be provided by the implementation to the tester # References to OAS spec schemas refer to schemas specified in qos-booking-and-assignment.yaml @@ -11,7 +11,7 @@ Feature: CAMARA QoS Booking and Assignment, vwip # Reserve a set of devices for a given qos profile, service area, scheduled future time and duration @qos_bookings_createBooking_201_success Scenario: Create a QoS booking with valid parameters - Given the resource "{apiRoot}/qos-booking-and-assignment/vwip/qos-bookings" + Given the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings" And the header "Content-Type" is set to "application/json" And the operationId is "createBooking" And the request body is set to a request body compliant with the schema at "/components/schemas/BookingInput" @@ -29,7 +29,7 @@ Feature: CAMARA QoS Booking and Assignment, vwip @qos_bookings_createBooking_201_success_echo Scenario: Create booking echoes selected request fields in response - Given the resource "{apiRoot}/qos-booking-and-assignment/vwip/qos-bookings" + Given the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings" And the operationId is "createBooking" And the request body is set to a request body compliant with the schema at "/components/schemas/BookingInput" And the request body property "$.qosProfile" is set to a valid QoS Profile as returned by QoS Profiles API @@ -49,7 +49,7 @@ Feature: CAMARA QoS Booking and Assignment, vwip # Given a bookingID, this GET operation gets the details of the original booking @qos_bookings_getBookingById_200_success Scenario: Get an existing QoS booking by bookingId - Given the resource "{apiRoot}/qos-booking-and-assignment/vwip/qos-bookings" + Given the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings" And an existing QoS booking with "bookingId" is created by the operation "createBooking" And the operationId is "getBookingById" When the request "getBookingById" is sent @@ -69,7 +69,7 @@ Feature: CAMARA QoS Booking and Assignment, vwip # This operation deletes a booking identified by bookingID. @qos_bookings_deleteBooking_200_success Scenario: Delete a QoS booking - Given the resource "{apiRoot}/qos-booking-and-assignment/vwip/qos-bookings" + Given the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings" And "bookingId" is created by operation "createBooking" And the operationId is "deleteBooking" When the request "deleteBooking" is sent @@ -86,7 +86,7 @@ Feature: CAMARA QoS Booking and Assignment, vwip # This operation assigns set of devices to a booking. @devices_assignDevices_201_success Scenario: Assign a set of devices to a QoS booking - Given the resource "{apiRoot}/qos-booking-and-assignment/vwip/qos-bookings/{bookingId}/devices/assign" + Given the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings/{bookingId}/devices/assign" And the "bookingId" is created by operation "createBooking" And the operationId is "assignDevices" And the request body complies with the OAS schema at "/components/schemas/DeviceAssignmentInput" @@ -106,7 +106,7 @@ Feature: CAMARA QoS Booking and Assignment, vwip # This operation releases a set of devices from a booking which are already assigned to the booking @devices_releaseDevices_200_success Scenario: Release one or more of already assigned devices from a QoS booking - Given the resource "{apiRoot}/qos-booking-and-assignment/vwip/qos-bookings/{bookingId}/devices/release" + Given the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings/{bookingId}/devices/release" And the "bookingId" is created by operation "createBooking" And the operationId is "releaseDevices" And the request body complies with the OAS schema at "/components/schemas/DeviceAssignmentInput" @@ -125,7 +125,7 @@ Feature: CAMARA QoS Booking and Assignment, vwip # This operation gets the list of devices assigned to a booking @devices_getDevicesByBookingId_200_success Scenario: Get a list of devices assigned to a QoS booking - Given the resource "{apiRoot}/qos-booking-and-assignment/vwip/qos-bookings/{bookingId}/devices" + Given the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings/{bookingId}/devices" And the "bookingId" is created by operation "createBooking" And the operationId is "getDevicesByBookingId" When the request "getDevicesByBookingId" is sent @@ -141,7 +141,7 @@ Feature: CAMARA QoS Booking and Assignment, vwip @devices_retrieveBooking_200_success Scenario: Get QoS Booking resource information details for a device Given a valid testing device with an existing QoS Booking, identified by the token or provided in the request body - And the resource "{apiRoot}/qos-booking-and-assignment/vwip/qos-bookings/retrieve" + And the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings/retrieve" When the request "retrieveBookingByDevice" is sent Then the response status code is 200 And the response header "Content-Type" is "application/json" From 954e234beb9dd2adee10a70d20d3ae992454dab6 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Fri, 29 Aug 2025 23:50:09 +0100 Subject: [PATCH 07/28] Update qos-booking.feature --- code/Test_definitions/qos-booking.feature | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/code/Test_definitions/qos-booking.feature b/code/Test_definitions/qos-booking.feature index c373b90..017c55b 100644 --- a/code/Test_definitions/qos-booking.feature +++ b/code/Test_definitions/qos-booking.feature @@ -1,4 +1,4 @@ -Feature: CAMARA QoS Booking API, vwip - API Operations +Feature: CAMARA QoS Booking API, v0.1.0 - API Operations # Input to be provided by the implementation to the tester # # Implementation indications: @@ -26,7 +26,7 @@ Feature: CAMARA QoS Booking API, vwip - API Operations @qos_booking_createBooking_01_success Scenario: Create a QoS booking with valid parameters - Given the resource "/qos-booking/vwip/device-qos-bookings" + Given the resource "/qos-booking/v0.1/device-qos-bookings" And the header "Content-Type" is set to "application/json" And the request body is set to a request body compliant with the schema at "/components/schemas/CreateBooking" And the request body property "$.qosProfile" is set to a valid QoS Profile as returned by QoS Profiles API @@ -45,7 +45,7 @@ Feature: CAMARA QoS Booking API, vwip - API Operations @qos_booking_getBooking_01_success Scenario: Get an existing QoS booking by bookingId - Given the resource "/qos-booking/vwip/device-qos-bookings/{bookingId}" + Given the resource "/qos-booking/v0.1/device-qos-bookings/{bookingId}" And an existing QoS booking created by operation createBooking And the path parameter "bookingId" is set to the value for that QoS booking When the request "getBookingById" is sent @@ -67,7 +67,7 @@ Feature: CAMARA QoS Booking API, vwip - API Operations Scenario: Delete a QoS booking Given that implementation deletes QoS booking synchronously And an existing QoS booking created by operation createBooking - And the resource "/qos-booking/vwip/device-qos-bookings/{bookingId}" + And the resource "/qos-booking/v0.1/device-qos-bookings/{bookingId}" And the path parameter "bookingId" is set to the value for that QoS booking When the request "deleteBooking" is sent Then the response status code is 204 @@ -78,7 +78,7 @@ Feature: CAMARA QoS Booking API, vwip - API Operations @qos_booking_retrieveBooking_01_success Scenario: Get QoS Booking resource information details for a device Given a valid testing device with an existing QoS Booking, identified by the token or provided in the request body - And the resource "/qos-booking/vwip/retrieve-device-qos-bookings" + And the resource "/qos-booking/v0.1/retrieve-device-qos-bookings" When the request "retrieveBookingByDevice" is sent Then the response status code is 200 And the response header "Content-Type" is "application/json" From de3f88055391f0945f04bc737dbd367aa4466be5 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Fri, 29 Aug 2025 23:51:01 +0100 Subject: [PATCH 08/28] Update qos-booking-and-assignment.feature --- .../qos-booking-and-assignment.feature | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/code/Test_definitions/qos-booking-and-assignment.feature b/code/Test_definitions/qos-booking-and-assignment.feature index 9bb8726..aa16792 100644 --- a/code/Test_definitions/qos-booking-and-assignment.feature +++ b/code/Test_definitions/qos-booking-and-assignment.feature @@ -11,7 +11,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 # Reserve a set of devices for a given qos profile, service area, scheduled future time and duration @qos_bookings_createBooking_201_success Scenario: Create a QoS booking with valid parameters - Given the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings" + Given the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings" And the header "Content-Type" is set to "application/json" And the operationId is "createBooking" And the request body is set to a request body compliant with the schema at "/components/schemas/BookingInput" @@ -29,7 +29,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 @qos_bookings_createBooking_201_success_echo Scenario: Create booking echoes selected request fields in response - Given the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings" + Given the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings" And the operationId is "createBooking" And the request body is set to a request body compliant with the schema at "/components/schemas/BookingInput" And the request body property "$.qosProfile" is set to a valid QoS Profile as returned by QoS Profiles API @@ -49,7 +49,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 # Given a bookingID, this GET operation gets the details of the original booking @qos_bookings_getBookingById_200_success Scenario: Get an existing QoS booking by bookingId - Given the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings" + Given the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings" And an existing QoS booking with "bookingId" is created by the operation "createBooking" And the operationId is "getBookingById" When the request "getBookingById" is sent @@ -69,7 +69,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 # This operation deletes a booking identified by bookingID. @qos_bookings_deleteBooking_200_success Scenario: Delete a QoS booking - Given the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings" + Given the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings" And "bookingId" is created by operation "createBooking" And the operationId is "deleteBooking" When the request "deleteBooking" is sent @@ -86,7 +86,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 # This operation assigns set of devices to a booking. @devices_assignDevices_201_success Scenario: Assign a set of devices to a QoS booking - Given the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings/{bookingId}/devices/assign" + Given the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings/{bookingId}/devices/assign" And the "bookingId" is created by operation "createBooking" And the operationId is "assignDevices" And the request body complies with the OAS schema at "/components/schemas/DeviceAssignmentInput" @@ -106,7 +106,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 # This operation releases a set of devices from a booking which are already assigned to the booking @devices_releaseDevices_200_success Scenario: Release one or more of already assigned devices from a QoS booking - Given the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings/{bookingId}/devices/release" + Given the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings/{bookingId}/devices/release" And the "bookingId" is created by operation "createBooking" And the operationId is "releaseDevices" And the request body complies with the OAS schema at "/components/schemas/DeviceAssignmentInput" @@ -125,7 +125,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 # This operation gets the list of devices assigned to a booking @devices_getDevicesByBookingId_200_success Scenario: Get a list of devices assigned to a QoS booking - Given the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings/{bookingId}/devices" + Given the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings/{bookingId}/devices" And the "bookingId" is created by operation "createBooking" And the operationId is "getDevicesByBookingId" When the request "getDevicesByBookingId" is sent @@ -141,7 +141,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 @devices_retrieveBooking_200_success Scenario: Get QoS Booking resource information details for a device Given a valid testing device with an existing QoS Booking, identified by the token or provided in the request body - And the resource "{apiRoot}/qos-booking-and-assignment/v0.3/qos-bookings/retrieve" + And the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings/retrieve" When the request "retrieveBookingByDevice" is sent Then the response status code is 200 And the response header "Content-Type" is "application/json" From 06fa6c62bffcfc53ebff62a9e761a6c1c2e420f9 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Fri, 29 Aug 2025 23:54:18 +0100 Subject: [PATCH 09/28] Update qos-booking-API-Readiness-Checklist.md --- .../qos-booking-API-Readiness-Checklist.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/documentation/API_documentation/qos-booking-API-Readiness-Checklist.md b/documentation/API_documentation/qos-booking-API-Readiness-Checklist.md index 962d901..d5a9f13 100644 --- a/documentation/API_documentation/qos-booking-API-Readiness-Checklist.md +++ b/documentation/API_documentation/qos-booking-API-Readiness-Checklist.md @@ -5,8 +5,8 @@ Checklist for qos-booking v0.1.0-rc.1 in r1.1 | Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information | |----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:| | 1 | API definition | M | M | M | M | Y | [link](/code/API_definitions/qos-booking.yaml) | -| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | [r3.2](https://github.com/camaraproject/Commonalities/releases/tag/r3.2) | -| 3 | Guidelines from ICM applied | O | M | M | M | Y | [r3.2](https://github.com/camaraproject/IdentityAndConsentManagement/releases/tag/r3.2) | +| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | [r3.3](https://github.com/camaraproject/Commonalities/releases/tag/r3.3) | +| 3 | Guidelines from ICM applied | O | M | M | M | Y | [r3.3](https://github.com/camaraproject/IdentityAndConsentManagement/releases/tag/r3.3) | | 4 | API versioning convention applied | M | M | M | M | Y | | | 5 | API documentation | M | M | M | M | Y | contained in API definition | | 6 | User stories | O | O | O | M | N | | @@ -16,4 +16,4 @@ Checklist for qos-booking v0.1.0-rc.1 in r1.1 | 10 | API release numbering convention applied | M | M | M | M | Y | | | 11 | Change log updated | M | M | M | M | Y | [link](/CHANGELOG.md) | | 12 | Previous public release was certified | O | O | O | M | N | | -| 13 | API description (for marketing) | O | O | M | M | Y | [wiki link](https://lf-camaraproject.atlassian.net/wiki/x/3YPVB) | +| 13 | API description (for marketing) | O | O | M | M | Y | [wiki link](https://lf-camaraproject.atlassian.net/wiki/x/3YPVB) | From 9c003e6974e733071dd9b8a9eda1e26fa528cda7 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Fri, 29 Aug 2025 23:56:42 +0100 Subject: [PATCH 10/28] Update qos-booking-and-assignment-API-Readiness-Checklist.md --- .../qos-booking-and-assignment-API-Readiness-Checklist.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/documentation/API_documentation/qos-booking-and-assignment-API-Readiness-Checklist.md b/documentation/API_documentation/qos-booking-and-assignment-API-Readiness-Checklist.md index c9c6094..9a9590e 100644 --- a/documentation/API_documentation/qos-booking-and-assignment-API-Readiness-Checklist.md +++ b/documentation/API_documentation/qos-booking-and-assignment-API-Readiness-Checklist.md @@ -5,8 +5,8 @@ Checklist for qos-booking-and-assignment v0.1.0-rc.1 in r1.1 | Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information | |----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:| | 1 | API definition | M | M | M | M | Y | [link](/code/API_definitions/qos-booking-and-assignment.yaml) | -| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | [r3.2](https://github.com/camaraproject/Commonalities/releases/tag/r3.2) | -| 3 | Guidelines from ICM applied | O | M | M | M | Y | [r3.2](https://github.com/camaraproject/IdentityAndConsentManagement/releases/tag/r3.2) | +| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | [r3.3](https://github.com/camaraproject/Commonalities/releases/tag/r3.3) | +| 3 | Guidelines from ICM applied | O | M | M | M | Y | [r3.3](https://github.com/camaraproject/IdentityAndConsentManagement/releases/tag/r3.3) | | 4 | API versioning convention applied | M | M | M | M | Y | | | 5 | API documentation | M | M | M | M | Y | contained in API definition | | 6 | User stories | O | O | O | M | N | | @@ -16,4 +16,4 @@ Checklist for qos-booking-and-assignment v0.1.0-rc.1 in r1.1 | 10 | API release numbering convention applied | M | M | M | M | Y | | | 11 | Change log updated | M | M | M | M | Y | [link](/CHANGELOG.md) | | 12 | Previous public release was certified | O | O | O | M | N | | -| 13 | API description (for marketing) | O | O | M | M | N | tbd until M4 | +| 13 | API description (for marketing) | O | O | M | M | Y | [wiki link](https://lf-camaraproject.atlassian.net/wiki/x/IYA5Cg) | From 66e5c170a8b5763fde916be51c365bf23b13188e Mon Sep 17 00:00:00 2001 From: Herbert Damker Date: Sat, 30 Aug 2025 13:40:15 +0200 Subject: [PATCH 11/28] Update qos-booking-and-assignment.yaml --- code/API_definitions/qos-booking-and-assignment.yaml | 1 - 1 file changed, 1 deletion(-) diff --git a/code/API_definitions/qos-booking-and-assignment.yaml b/code/API_definitions/qos-booking-and-assignment.yaml index c9517eb..753bf65 100644 --- a/code/API_definitions/qos-booking-and-assignment.yaml +++ b/code/API_definitions/qos-booking-and-assignment.yaml @@ -2038,4 +2038,3 @@ components: summary: No bookings found for the device description: No bookings are found for the device, value contains only empty array value: [] - From 9d138c076f45e85f1b26f65ae0c9d5facbd9fc8c Mon Sep 17 00:00:00 2001 From: Herbert Damker Date: Sat, 30 Aug 2025 13:48:57 +0200 Subject: [PATCH 12/28] Update qos-booking.yaml --- code/API_definitions/qos-booking.yaml | 1 - 1 file changed, 1 deletion(-) diff --git a/code/API_definitions/qos-booking.yaml b/code/API_definitions/qos-booking.yaml index 0db08f8..49c5dca 100644 --- a/code/API_definitions/qos-booking.yaml +++ b/code/API_definitions/qos-booking.yaml @@ -1486,4 +1486,3 @@ components: summary: No bookings found for the device description: An empty array is returned when no bookings are found for the device value: [] - From fc0942da999682843a6f4a00f2355142e76f3b53 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Mon, 1 Sep 2025 11:27:51 +0100 Subject: [PATCH 13/28] Update qos-booking-API-Readiness-Checklist.md --- .../API_documentation/qos-booking-API-Readiness-Checklist.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/API_documentation/qos-booking-API-Readiness-Checklist.md b/documentation/API_documentation/qos-booking-API-Readiness-Checklist.md index d5a9f13..aad6525 100644 --- a/documentation/API_documentation/qos-booking-API-Readiness-Checklist.md +++ b/documentation/API_documentation/qos-booking-API-Readiness-Checklist.md @@ -1,6 +1,6 @@ # API Readiness Checklist -Checklist for qos-booking v0.1.0-rc.1 in r1.1 +Checklist for qos-booking v0.1.0 in r1.2 | Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information | |----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:| From a9c12d7b5e8cfc4a37ad3ba47f84833382a14333 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Mon, 1 Sep 2025 11:28:13 +0100 Subject: [PATCH 14/28] Update qos-booking-and-assignment-API-Readiness-Checklist.md --- .../qos-booking-and-assignment-API-Readiness-Checklist.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/API_documentation/qos-booking-and-assignment-API-Readiness-Checklist.md b/documentation/API_documentation/qos-booking-and-assignment-API-Readiness-Checklist.md index 9a9590e..5694767 100644 --- a/documentation/API_documentation/qos-booking-and-assignment-API-Readiness-Checklist.md +++ b/documentation/API_documentation/qos-booking-and-assignment-API-Readiness-Checklist.md @@ -1,6 +1,6 @@ # API Readiness Checklist -Checklist for qos-booking-and-assignment v0.1.0-rc.1 in r1.1 +Checklist for qos-booking-and-assignment v0.1.0 in r1.2 | Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information | |----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:| From cf76f90696b7063d13b1917c6eff560f7ffbf5a0 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Mon, 1 Sep 2025 11:32:18 +0100 Subject: [PATCH 15/28] Update CHANGELOG.md Co-authored-by: Herbert Damker --- CHANGELOG.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 389b45f..cbaccd6 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -73,6 +73,7 @@ The API definition(s) are based on ### Removed * Remove unnecessary spaces, tabs, lfs in qos-booking-and-assignment.feature file by @RmaTMO in #44 + **Full Changelog**: https://github.com/camaraproject/QoSBooking/commits/r1.2 # r1.1 ## Release Notes From a281b30849f4e146800a48a588bf4d08d651c036 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Mon, 1 Sep 2025 14:32:49 +0100 Subject: [PATCH 16/28] Update CHANGELOG.md --- CHANGELOG.md | 28 +++------------------------- 1 file changed, 3 insertions(+), 25 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index cbaccd6..2eef6fe 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -36,17 +36,7 @@ The API definition(s) are based on - OpenAPI [YAML spec file](https://github.com/camaraproject/QoSBooking/blob/r1.2/code/API_definitions/qos-booking.yaml) ### Added -* N/A - -### Changed -* N/A - -### Fixed -* Align qos-booking with Commonalities r3.3 by @jlurien in [#40](https://github.com/camaraproject/QoSBooking/pull/40) -* Fix files of qos-booking for compliance with centralised linting rules by @Masa8106 in [#41](https://github.com/camaraproject/QoSBooking/pull/41) - -### Removed -* N/A +* Initial contribution of the QoS Booking API
which includes all alignments and fixes since the pre-release ## qos-booking-and-assignment v0.1.0 @@ -58,22 +48,10 @@ The API definition(s) are based on - OpenAPI [YAML spec file](https://github.com/camaraproject/QoSBooking/blob/r1.2/code/API_definitions/qos-booking-and-assignment.yaml) ### Added -* Added examples to address the issue #33 by @RamTMO in [#35](https://github.com/camaraproject/QoSBooking/pull/35) - -### Changed -* N/A - -### Fixed -* Fix DeviceResponse Issue #30 in QoS Booking and Assignment by @RmaTMO in [#34](https://github.com/camaraproject/QoSBooking/pull/34) -* Align qos-booking with Commonalities r3.3 by @jlurien in [#40](https://github.com/camaraproject/QoSBooking/pull/40) -* Update qos-booking-and-assignment.yaml to support issues by @RmaTMO in [#43](https://github.com/camaraproject/QoSBooking/pull/43) -* Fix DeviceCount related issues by @RmaTMO in [#48](https://github.com/camaraproject/QoSBooking/pull/48) -* bookingId related issues & remaining linting issues by @RmaTMO in [#50](https://github.com/camaraproject/QoSBooking/pull/50) +* Initial contribution of the QoS Booking and Assignment API
which includes all alignments and fixes since the pre-release -### Removed -* Remove unnecessary spaces, tabs, lfs in qos-booking-and-assignment.feature file by @RmaTMO in #44 +**Full Changelog**: https://github.com/camaraproject/QoSBooking/commits/r1.2 - **Full Changelog**: https://github.com/camaraproject/QoSBooking/commits/r1.2 # r1.1 ## Release Notes From 00cdc70be83a9d8b2e44c1ac0ce0c66062661a1a Mon Sep 17 00:00:00 2001 From: Jose Luis Urien Date: Thu, 4 Sep 2025 15:52:15 +0200 Subject: [PATCH 17/28] Update CHANGELOG.md --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 2eef6fe..dd72135 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -18,7 +18,7 @@ The below sections record the changes for each API version in each release as fo ## Release Notes -This release contains the definition and documentation of +This public release contains the definition and documentation of * qos-booking v0.1.0 * qos-booking-and-assignment v0.1.0 From b5412e9838ccdbbc3b8368b7be6631f17a5fb15a Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Thu, 11 Sep 2025 12:38:07 +0100 Subject: [PATCH 18/28] Update CHANGELOG.md --- CHANGELOG.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index dd72135..f6f1fee 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -28,7 +28,7 @@ The API definition(s) are based on ## qos-booking v0.1.0 -**qos-booking v0.1.0 is the first initial release of this new API.** +**qos-booking v0.1.0 is the first public release of this new API.** - API definition **with inline documentation**: - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/QoSBooking/r1.2/code/API_definitions/qos-booking.yaml&nocors) @@ -40,7 +40,7 @@ The API definition(s) are based on ## qos-booking-and-assignment v0.1.0 -**qos-booking-and-assignment v0.1.0 is the first initial release of this new API.** +**qos-booking-and-assignment v0.1.0 is the public initial release of this new API.** - API definition **with inline documentation**: - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/QoSBooking/r1.2/code/API_definitions/qos-booking-and-assignment.yaml&nocors) From 6aa200197b2ff2806c38cbde7e7e50f5160dc1c3 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Thu, 11 Sep 2025 12:40:20 +0100 Subject: [PATCH 19/28] Update CHANGELOG.md --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index f6f1fee..fc2502c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -40,7 +40,7 @@ The API definition(s) are based on ## qos-booking-and-assignment v0.1.0 -**qos-booking-and-assignment v0.1.0 is the public initial release of this new API.** +**qos-booking-and-assignment v0.1.0 is the first public release of this new API.** - API definition **with inline documentation**: - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/QoSBooking/r1.2/code/API_definitions/qos-booking-and-assignment.yaml&nocors) From 76f999867c2f59e76db863230c13ec2898b01c5e Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Thu, 11 Sep 2025 12:43:21 +0100 Subject: [PATCH 20/28] Update code/Test_definitions/qos-booking-and-assignment.feature Co-authored-by: Kevin Smith --- code/Test_definitions/qos-booking-and-assignment.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/Test_definitions/qos-booking-and-assignment.feature b/code/Test_definitions/qos-booking-and-assignment.feature index c61bc4c..5c9884f 100644 --- a/code/Test_definitions/qos-booking-and-assignment.feature +++ b/code/Test_definitions/qos-booking-and-assignment.feature @@ -11,7 +11,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 # Reserve a set of devices for a given qos profile, service area, scheduled future time and duration @qos_bookings_createBooking_201_success Scenario: Create a QoS booking with valid parameters - Given the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings" + Given the resource "/qos-booking-and-assignment/v0.1/qos-bookings" And the header "Content-Type" is set to "application/json" And the operationId is "createBooking" And the request body is set to a request body compliant with the schema at "/components/schemas/BookingInput" From f0012485e45007e2ca1e7d6771d0ab50c7deac6c Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Thu, 11 Sep 2025 12:43:36 +0100 Subject: [PATCH 21/28] Update code/Test_definitions/qos-booking-and-assignment.feature Co-authored-by: Kevin Smith --- code/Test_definitions/qos-booking-and-assignment.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/Test_definitions/qos-booking-and-assignment.feature b/code/Test_definitions/qos-booking-and-assignment.feature index 5c9884f..d8ed634 100644 --- a/code/Test_definitions/qos-booking-and-assignment.feature +++ b/code/Test_definitions/qos-booking-and-assignment.feature @@ -29,7 +29,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 @qos_bookings_createBooking_201_success_echo Scenario: Create booking echoes selected request fields in response - Given the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings" + Given the resource "/qos-booking-and-assignment/v0.1/qos-bookings" And the operationId is "createBooking" And the request body is set to a request body compliant with the schema at "/components/schemas/BookingInput" And the request body property "$.qosProfile" is set to a valid QoS Profile as returned by QoS Profiles API From fb967d6d031ed7544ee42ddb7ac8a92eef451780 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Thu, 11 Sep 2025 12:43:52 +0100 Subject: [PATCH 22/28] Update code/Test_definitions/qos-booking-and-assignment.feature Co-authored-by: Kevin Smith --- code/Test_definitions/qos-booking-and-assignment.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/Test_definitions/qos-booking-and-assignment.feature b/code/Test_definitions/qos-booking-and-assignment.feature index d8ed634..2894165 100644 --- a/code/Test_definitions/qos-booking-and-assignment.feature +++ b/code/Test_definitions/qos-booking-and-assignment.feature @@ -49,7 +49,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 # Given a bookingID, this GET operation gets the details of the original booking @qos_bookings_getBookingById_200_success Scenario: Get an existing QoS booking by bookingId - Given the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings" + Given the resource "/qos-booking-and-assignment/v0.1/qos-bookings" And an existing QoS booking with "bookingId" is created by the operation "createBooking" And the operationId is "getBookingById" When the request "getBookingById" is sent From f6fa98441bf68022ad2a1a60e8161365f3e6aeaf Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Thu, 11 Sep 2025 12:44:02 +0100 Subject: [PATCH 23/28] Update code/Test_definitions/qos-booking-and-assignment.feature Co-authored-by: Kevin Smith --- code/Test_definitions/qos-booking-and-assignment.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/Test_definitions/qos-booking-and-assignment.feature b/code/Test_definitions/qos-booking-and-assignment.feature index 2894165..67ad5c9 100644 --- a/code/Test_definitions/qos-booking-and-assignment.feature +++ b/code/Test_definitions/qos-booking-and-assignment.feature @@ -69,7 +69,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 # This operation deletes a booking identified by bookingID. @qos_bookings_deleteBooking_200_success Scenario: Delete a QoS booking - Given the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings" + Given the resource "/qos-booking-and-assignment/v0.1/qos-bookings" And "bookingId" is created by operation "createBooking" And the operationId is "deleteBooking" When the request "deleteBooking" is sent From cb8d0e25f2601680a32e4e6d88843a26cf7daef7 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Thu, 11 Sep 2025 12:44:15 +0100 Subject: [PATCH 24/28] Update code/Test_definitions/qos-booking-and-assignment.feature Co-authored-by: Kevin Smith --- code/Test_definitions/qos-booking-and-assignment.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/Test_definitions/qos-booking-and-assignment.feature b/code/Test_definitions/qos-booking-and-assignment.feature index 67ad5c9..e6f8740 100644 --- a/code/Test_definitions/qos-booking-and-assignment.feature +++ b/code/Test_definitions/qos-booking-and-assignment.feature @@ -86,7 +86,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 # This operation assigns set of devices to a booking. @devices_assignDevices_201_success Scenario: Assign a set of devices to a QoS booking - Given the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings/{bookingId}/devices/assign" + Given the resource "/qos-booking-and-assignment/v0.1/qos-bookings/{bookingId}/devices/assign" And the "bookingId" is created by operation "createBooking" And the operationId is "assignDevices" And the request body complies with the OAS schema at "/components/schemas/DeviceAssignmentInput" From a256eba16f47b4a847574bda3d1fdcfb367b9644 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Thu, 11 Sep 2025 12:44:26 +0100 Subject: [PATCH 25/28] Update code/Test_definitions/qos-booking-and-assignment.feature Co-authored-by: Kevin Smith --- code/Test_definitions/qos-booking-and-assignment.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/Test_definitions/qos-booking-and-assignment.feature b/code/Test_definitions/qos-booking-and-assignment.feature index e6f8740..aa4221e 100644 --- a/code/Test_definitions/qos-booking-and-assignment.feature +++ b/code/Test_definitions/qos-booking-and-assignment.feature @@ -106,7 +106,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 # This operation releases a set of devices from a booking which are already assigned to the booking @devices_releaseDevices_200_success Scenario: Release one or more of already assigned devices from a QoS booking - Given the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings/{bookingId}/devices/release" + Given the resource "/qos-booking-and-assignment/v0.1/qos-bookings/{bookingId}/devices/release" And the "bookingId" is created by operation "createBooking" And the operationId is "releaseDevices" And the request body complies with the OAS schema at "/components/schemas/DeviceAssignmentInput" From 6f8c60658b0f13d64fd77412eeec1c0ad512f365 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Thu, 11 Sep 2025 12:45:28 +0100 Subject: [PATCH 26/28] Update code/Test_definitions/qos-booking-and-assignment.feature Co-authored-by: Kevin Smith --- code/Test_definitions/qos-booking-and-assignment.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/Test_definitions/qos-booking-and-assignment.feature b/code/Test_definitions/qos-booking-and-assignment.feature index aa4221e..fdfc577 100644 --- a/code/Test_definitions/qos-booking-and-assignment.feature +++ b/code/Test_definitions/qos-booking-and-assignment.feature @@ -125,7 +125,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 # This operation gets the list of devices assigned to a booking @devices_getDevicesByBookingId_200_success Scenario: Get a list of devices assigned to a QoS booking - Given the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings/{bookingId}/devices" + Given the resource "/qos-booking-and-assignment/v0.1/qos-bookings/{bookingId}/devices" And the "bookingId" is created by operation "createBooking" And the operationId is "getDevicesByBookingId" When the request "getDevicesByBookingId" is sent From 167351cc688f49e54b9730070d3a02bf52b24f96 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Thu, 11 Sep 2025 12:45:42 +0100 Subject: [PATCH 27/28] Update code/Test_definitions/qos-booking-and-assignment.feature Co-authored-by: Kevin Smith --- code/Test_definitions/qos-booking-and-assignment.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/Test_definitions/qos-booking-and-assignment.feature b/code/Test_definitions/qos-booking-and-assignment.feature index fdfc577..ffe1713 100644 --- a/code/Test_definitions/qos-booking-and-assignment.feature +++ b/code/Test_definitions/qos-booking-and-assignment.feature @@ -141,7 +141,7 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 @devices_retrieveBooking_200_success Scenario: Get QoS Booking resource information details for a device Given a valid testing device with an existing QoS Booking, identified by the token or provided in the request body - And the resource "{apiRoot}/qos-booking-and-assignment/v0.1/qos-bookings/retrieve" + And the resource "/qos-booking-and-assignment/v0.1/qos-bookings/retrieve" When the request "retrieveBookingByDevice" is sent Then the response status code is 200 And the response header "Content-Type" is "application/json" From 54d94a2959ed0edb6f21ec0a6a3a0179ff2b1f00 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Thu, 11 Sep 2025 12:46:33 +0100 Subject: [PATCH 28/28] Update code/Test_definitions/qos-booking-and-assignment.feature Co-authored-by: Kevin Smith --- code/Test_definitions/qos-booking-and-assignment.feature | 3 +++ 1 file changed, 3 insertions(+) diff --git a/code/Test_definitions/qos-booking-and-assignment.feature b/code/Test_definitions/qos-booking-and-assignment.feature index ffe1713..742f6ae 100644 --- a/code/Test_definitions/qos-booking-and-assignment.feature +++ b/code/Test_definitions/qos-booking-and-assignment.feature @@ -1,5 +1,8 @@ Feature: CAMARA QoS Booking and Assignment, v0.1.0 # Input to be provided by the implementation to the tester + # + # Implementation indications: + # * apiRoot: API root of the server URL # References to OAS spec schemas refer to schemas specified in qos-booking-and-assignment.yaml Background: Common QoS Booking setup