You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The validator comes back with a warning for the content of some of our example responses:
Message : Enum value "option1" must be "single_select".
Path : paths./tekton_pipelines/{pipeline_id}/properties.post.requestBody.content.application/json.examples.single_select_env_properties.value.enum.0
Line : 1119
This is arising in 9 places in our API yaml. The full yaml file can be seen here
Oops yeah got the tools mixed up, but same problem with latest validator
$ npm ls -g ibm-openapi-validator
C:\Users\I72022754\AppData\Roaming\npm
└── ibm-openapi-validator@1.1.2
$ npm run openapi lint
> bash ./scripts/terraform/openapi.sh "lint"
Lint openapi.yaml
IBM OpenAPI Validator (validator: 1.1.2; ruleset: 1.1.1), @Copyright IBM Corporation 2017, 2023.
Validation Results for ./tekton/controllers/spec/v2/openapi.yaml:
Summary:
Total number of errors : 0
Total number of warnings : 9
Warnings:
3 (30%) : Enum value "option1" must be "single_select".
3 (30%) : Enum value "option2" must be "single_select".
3 (30%) : Enum value "option3" must be "single_select".
Complete
@briangleeson I was able to reproduce but identified this issue is coming from a Spectral rule called typed-enum, which we did not implement and don't maintain. I'd recommend opening an issue against their project here or seeing if there's anything obviously wrong with their implementation here if you're interested in opening a PR.
Version:
ibm-openapi-validator@0.91.0
The validator comes back with a warning for the content of some of our example responses:
This is arising in 9 places in our API yaml. The full yaml file can be seen here
This is one example:
Schema for the enum:
It seems like the fact we are using the term
enum
for one of the properties in our API schema is confusing the validatorThe text was updated successfully, but these errors were encountered: