feat: add batch create/update/delete item contracts

[shalk]

Summary

• Add three new Item Management operations for submitting a list of namespace items in one call:
  • POST .../items/batch-create (batchCreateItems)
  • PUT .../items/batch-update (batchUpdateItems)
  • POST .../items/batch-delete (batchDeleteItems)
• Bump spec version to 0.3.11 and add a CHANGELOG entry
• Add contract tests validating the new paths/operationIds/schemas

Motivation

Apollo's OpenAPI item endpoints only support single-item create/update/delete (plus namespace-text replace and cross-namespace sync/diff). There's no operation for submitting a structured batch of creates/updates/deletes against a single namespace. This is a companion PR to a corresponding apolloconfig/apollo change that implements these operations against the existing internal ItemChangeSets batch plumbing.

Test plan

• ./generate.sh --verify
• python -m unittest tests/test_item_batch_contract.py

🤖 Generated with Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 7c8e8450-b043-4a03-963d-197907eb9a71

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[nobodyiam]

The three batch paths and generated Spring signatures align with the companion implementation, and the local contract and generation checks pass. One contract mismatch remains.

Please fix this blocking item before updating:

1. In apollo-openapi.yaml, express the runtime batch validation in the contract: add minItems: 1 to all three request arrays, add minLength: 1 to the batch-delete key items, and document 400 with ExceptionResponse for batchDeleteItems. Please extend tests/test_item_batch_contract.py accordingly. The companion controller rejects these inputs with HTTP 400, so v0.3.11 should not advertise them as valid or leave that response undocumented.

[nobodyiam]

I rechecked head 62d3b987d3da8e2ee1e6de8639f0b345671abc6b. The requested contract/runtime alignment is now present: all three request arrays have minItems: 1, batch-delete keys have minLength: 1, and batchDeleteItems documents the 400 ExceptionResponse. All 13 repository Python tests pass, ./generate.sh --verify passes, and the generated ItemManagementApi signatures align with apolloconfig/apollo#5665. I found no remaining blocking contract issue. The existing CHANGES_REQUESTED state still needs an explicit maintainer re-review before the contract is merged and released.

Note: this reply was generated and posted automatically by AI for initial triage; a maintainer will follow up if needed.

[nobodyiam]

Rechecked head 62d3b987d3da8e2ee1e6de8639f0b345671abc6b. The previous blocking contract/runtime mismatch is fully resolved: all three request arrays enforce minItems: 1, batch-delete keys enforce minLength: 1, and batchDeleteItems documents the 400 ExceptionResponse, with corresponding contract coverage.

All 13 repository tests pass locally, OpenAPI validation and Portal generation verification pass, and the generated Spring project compiles successfully. The generated signatures also remain aligned with the latest companion implementation in apolloconfig/apollo#5665.

No remaining blocking findings. Approved.

Before merge, please approve and run the pending General CI Checks workflow and ensure all jobs pass.