boldtrail/Confluent Schema Registry Action
Validate and update schemas in Confluent-compatible schema registries
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Nov 12, 2025
- License
- MIT
Pinned Snippet
uses: boldtrail/confluent-schema-registry-action@717ef944adbe758fde85180c2874387eed66c1b9 # v1.0tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| schema-file | Path to the schema file | yes | — |
| subject-name | Subject name in the schema registry | yes | — |
| subject-namespace | Subject namespace in the schema registry | no | — |
| schema-compatibility | Compatibility level for the schema | no | BACKWARD |
| registry-url | URL of the Schema Registry | yes | http://localhost:8081 |
| username | Username for registry authentication | no | — |
| password | Password for registry authentication | no | — |
| schema-type | Schema type (AVRO, JSON, or PROTOBUF) | no | AVRO |
| environment | Environment name for namespacing (e.g., dev, staging, prod) | no | — |
| subject-pattern | Pattern for namespaced subjects, use {env}, {namespace}, and {name} placeholders | no | {namespace}.{name} |
| register-new | Whether or not to register a new version of the schema | no | true |
| check-compatibility | Whether or not to check compatibility of schema changes | no | true |
Outputs
| name | description |
|---|---|
| updated | Whether the schema was updated in the registry |
| compatible | Whether the schema is compatible with the registry |
| schema_id | The global ID of the registered schema |
| namespaced_subject | The actual subject name used in the registry (with environment namespace if applicable) |