Skip to content

fix: add missing 'type' on CloudEvent and Status schemas#555

Merged
hdamker merged 1 commit into
camaraproject:mainfrom
hdamker:fix/s016-missing-type-cloudevent-status
May 29, 2026
Merged

fix: add missing 'type' on CloudEvent and Status schemas#555
hdamker merged 1 commit into
camaraproject:mainfrom
hdamker:fix/s016-missing-type-cloudevent-status

Conversation

@hdamker
Copy link
Copy Markdown
Collaborator

@hdamker hdamker commented Apr 29, 2026

What type of PR is this?

correction

What this PR does / why we need it:

Adds three missing type: declarations flagged by CAMARA Validation rule S-016 (camara-schema-type-check):

  • code/API_definitions/qos-provisioning.yaml: type: object on CloudEvent, type: string on Status
  • code/API_definitions/quality-on-demand.yaml: type: object on CloudEvent

Three single-line additions. No other changes.

Which issue(s) this PR fixes:

Fixes #554

Special notes for reviewers:

This is a temporary fix. The durable solution is to refactor both API definitions to consume the canonical Commonalities common schemas via $ref into code/common/CAMARA_event_common.yaml (and CAMARA_common.yaml), as enabled by Commonalities r4.2 — removing the inlined CloudEvent copies entirely.

Changelog input

 release-note
Fix three S-016 validation findings: add missing 'type' declarations on CloudEvent (×2) and Status schemas.

Additional documentation

This section can be blank.

docs

@hdamker hdamker merged commit 97dd59d into camaraproject:main May 29, 2026
2 checks passed
@hdamker hdamker deleted the fix/s016-missing-type-cloudevent-status branch May 29, 2026 13:57
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.

Three S-016 validation errors: missing 'type' on CloudEvent (×2) and Status schemas

2 participants