Skip to content

Sync common files from Commonalities r4.4 - #191

Merged
tlohmar merged 1 commit into
mainfrom
sync-common/r4.4
Sep 25, 2026
Merged

tlohmar merged 1 commit into
mainfrom
sync-common/r4.4

Conversation

@camara-release-automation

Copy link
Copy Markdown
Contributor

Warning

This branch is owned by Release Automation and is rebuilt from main on every run.
Do not commit fixes to this branch — any commits here are overwritten the next time the sync runs.

Automated sync of code/common/ files from camaraproject/Commonalities at release tag r4.4.

This PR was created by release automation because the cached Commonalities files were out of sync with the declared dependency in release-plan.yaml.

What changed:

  • Updated files in code/common/ to match Commonalities r4.4
  • Added/updated .sync-manifest.yaml with file integrity hashes

How to handle this PR:

  • Validation green — review and merge.
  • Validation red — choose one:
    • (recommended) fix the errors on main, then re-trigger the sync; this PR is rebuilt from the new main HEAD with the corrected content.
    • merge this PR with the errors and fix them on main afterwards.

To re-trigger the sync, run the CAMARA Release Automation workflow from the repository's Actions tab.

/create-snapshot is blocked until common files are in sync.

@camara-validation

Copy link
Copy Markdown

CAMARA Validation — PASS (with warnings)

0 errors, 4 warnings, 10 hints | Profile: standard

View full results

@tlohmar tlohmar left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looks ok. Maybe better to first merge PR #179.

@tlohmar
tlohmar merged commit 381f837 into main Sep 25, 2026
3 checks passed
jimfengjinhua added a commit to jimfengjinhua/DedicatedNetworks that referenced this pull request Oct 2, 2026
Align the four API definitions with Commonalities r4.4 (0.9.0), whose
common files were synced in camaraproject#191.

- Bump info.x-camara-commonalities to 0.9 and apply the reworded
  "Additional CAMARA error responses" info.description template.
- Replace the deprecated Generic* error responses per operation with the
  r4.4 catalogue: BadRequest400, BadRequestWithRange400, NotFound404,
  Unauthenticated401 and PermissionDenied403, and SinkGone410 on the
  callbacks. This also drops INVALID_TOKEN_CONTEXT, which r4.4 removed
  from 403.
- List operations use BadRequest400, as invalid page/perPage values
  return 400 INVALID_ARGUMENT (Design Guide 4.1).
- Keep local responses only where the catalogue does not fit: a 400 on
  POST /networks and POST /accesses that adds the sink-related codes
  INVALID_CREDENTIAL, INVALID_TOKEN and INVALID_SINK, the
  DEDICATED_NETWORK.* 404 codes on POST /networks, a 404
  DEDICATED_NETWORK_ACCESSES.NETWORK_IDENTIFIER_NOT_FOUND on
  POST /accesses, and narrowed 409s on POST /accesses (INCOMPATIBLE_STATE)
  and the add/remove devices operations (ABORTED, INCOMPATIBLE_STATE).
- Example labels: use the API prefix for locally defined examples, keep
  GENERIC_ for references to common examples, and define the shared 409
  INCOMPATIBLE_STATE example once.
- Replace the two inline sink definitions with the common Sink schema.
- Test definitions: add createAccess_404.01_networkid_not_found, and make
  the pagination scenarios of listNetworks, readNetworkProfiles and
  retrieveNetworkServiceAreas expect INVALID_ARGUMENT, renaming their
  tags from *_out_of_range_pagination to *_invalid_pagination.
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