core-command swagger file has incorrect example and missing PUT parameters #4629
Assignees
Labels
bug
Something isn't working
Comments
vli11
added a commit
to vli11/edgex-go
that referenced
this issue
Aug 12, 2023
…parameters Closes: edgexfoundry#4629 Signed-off-by: Valina Li <valina.li@intel.com>
vli11
added a commit
to vli11/edgex-go
that referenced
this issue
Aug 12, 2023
fixing core-command swagger file that has incorrect example and missing PUT parameters Closes: edgexfoundry#4629 Signed-off-by: Valina Li <valina.li@intel.com>
vli11
added a commit
to vli11/edgex-go
that referenced
this issue
Aug 12, 2023
fixing core-command swagger file that has incorrect example and missing PUT parameters Closes: edgexfoundry#4629 Signed-off-by: Valina Li <valina.li@intel.com>
lenny-goodell
pushed a commit
that referenced
this issue
Aug 14, 2023
fixing core-command swagger file that has incorrect example and missing PUT parameters Closes: #4629 Signed-off-by: Valina Li <valina.li@intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐞 Bug Report
Affected Services [REQUIRED]
core-command swagger file has incorrect example and missing PUT parameters, this cause low fuzzing test coverage
The issue is located in: openapi/v3/core-command.yaml
Is this a regression? no
noDescription and Minimal Reproduction [REQUIRED]
following #4569 to perform fuzzing test, you can see core-command fuzzing test coverage is only 4/7.
with this fix, run the fuzzing test again, the coverage should be 6/7.
🔥 Exception or Error
🌍 Your Environment
Deployment Environment:
**EdgeX Version 3.0
Anything else relevant?
The text was updated successfully, but these errors were encountered: