Repository navigation
update the yaml file about esim-remote-management api to solve issue30 and issue31 #39
ChinaUnicomXiaoDongruicamara-validation.yml
on: pull_request
validation
/
Validate
29s
Annotations
1 warning and 2 notices
|
CloudEvent type format is wrong:
code/API_definitions/esim-remote-management.yaml#L1
[P-015] Event type 'io.camara.esim.profile.download.completed' does not match expected format 'org.camaraproject.<api-name>.<vN>.<event-name>' | Event type 'io.camara.esim.profile.operation.completed' does not match expected format 'org.camaraproject.<api-name>.<vN>.<event-name>' | Suggestion: Define a named event type schema (e.g. ApiEventType) that constrains the CloudEvent `type` value via allOf, rather than inlining the enum directly in CloudEvent.properties.type.enum. See the implicit-events API template in Commonalities artifacts/api-templates/ (tracked in camaraproject/Commonalities#608).
|
|
Tag name must be Title Case:
code/API_definitions/esim-remote-management.yaml#L79
[S-021] Tag name 'eSIM Remote Management' is not Title Case. Use e.g. 'Quality On Demand' instead of 'quality-on-demand'.
|
|
externalDocs.description must match the DG template:
code/API_definitions/esim-remote-management.yaml#L1
[P-039] externalDocs.description in code/API_definitions/esim-remote-management.yaml is 'Project documentation at CAMARA' — expected 'Product documentation at CAMARA' | Suggestion: Set externalDocs.description to exactly "Product documentation at CAMARA".
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
validation-bundled-specs
|
6.14 KB |
sha256:af4e5bbac79be979a4ec7bfbcc2823a8a516725b4e2c40e7b44be59813a1c80d
|
|