Skip to content

ci: validate AsyncAPI payload examples - #237

Merged
ramioooz merged 1 commit into
ci/235-asyncapi-validationfrom
ci/61-contract-example-validation
Sep 5, 2026
Merged

ramioooz merged 1 commit into
ci/235-asyncapi-validationfrom
ci/61-contract-example-validation

Conversation

@ramioooz

@ramioooz ramioooz commented Sep 5, 2026

Copy link
Copy Markdown
Member

Summary

  • Validate every representative AsyncAPI payload example against its declared local schema.
  • Cover required fields, constants, enums, formats, patterns, arrays, object properties, allOf, oneOf, anyOf, if/then, and not used by the current contracts.
  • Keep the check dependency-free and extend the existing ci: validate AsyncAPI event contracts #236 validator without adding another workflow or generated Java model library.

Scope boundary

This is a stacked PR on #236. It does not add producers, consumers, DTOs, runtime Schema Registry credentials, Kafka topics, AWS/UAT/PROD configuration, or a second CI job. Live Registry compatibility and changed-subject comparison remain platform/release responsibilities.

Related Issues And PRs

Verification

  • ruby scripts/validate_asyncapi_contracts.rb
  • ruby -c scripts/validate_asyncapi_contracts.rb
  • Positive and negative in-memory schema checks
  • git diff --check

Security Confirmation

  • No credentials, tokens, private keys, or real secrets added.
  • No production endpoints or environment-specific runtime configuration added.

@ramioooz
ramioooz merged commit ce38e6e into ci/235-asyncapi-validation Sep 5, 2026
1 check passed
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.

1 participant