Skip to content

Conversation

@maksim-gladkov
Copy link

2.9 Batch Resource Operations

@maksim-gladkov maksim-gladkov changed the title Batch Resource Operations 2.9 rules 2.9 Batch Resource Operations rules Apr 30, 2025
description: "This rule checks whether resources for creation, update, and deletion in batches are specified in the request body."

- id: 2.9.4
title: "Batch Resource Operations"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @maksim-gladkov do you know how to distinguish synchronous and asynchronous operation in api spec?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @anton-sidelnikov, perhaps we may check whether response payload contains 'job_id' or 'task_id'. This means that operation is asynchronous.


- id: 2.9.6
title: "Batch Resource Operations"
message: "If API supports 'all resources success' or 'all resources failure', then status of each indiviadual resource must be omitted in the response."
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and this, i dont understand how to distinguish all success and all failure, maybe you know?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @vladimirhasko , can we request to provide this information from HW side in comment section maybe? Or somehow marked an API for batch operations whether its supports 'all success/all failure'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants