Re:Tried to regenerate codes and tests via swagger, but..

[ktrysmt]

origin: https://bitbucket.org/api/swagger.json

[ktrysmt]

tool: https://editor.swagger.io/

the errors outputed..

That's too bad.

Detail is below;

Structural error at definitions.report_annotation.allOf.1.properties.external_id.required
should be array
Jump to line 2003
Structural error at definitions.report_annotation.allOf.1.properties.summary.required
should be array
Jump to line 2024
Structural error at definitions.report.allOf.1.properties.title.required
should be array
Jump to line 2090
Structural error at definitions.report.allOf.1.properties.details.required
should be array
Jump to line 2094
Structural error at definitions.report.allOf.1.properties.external_id.required
should be array
Jump to line 2098
Structural error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports/test_cases/{test_case_uuid}/test_case_reasons.get
should have required property 'responses'
missingProperty: responses
Jump to line 6445
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports/test_cases/{test_case_uuid}/test_case_reasons
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 6445
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports/test_cases/{test_case_uuid}/test_case_reasons
Declared path parameter "repo_slug" needs to be defined as a path parameter at either the path or operation level
Jump to line 6445
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports/test_cases/{test_case_uuid}/test_case_reasons
Declared path parameter "pipeline_uuid" needs to be defined as a path parameter at either the path or operation level
Jump to line 6445
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports/test_cases/{test_case_uuid}/test_case_reasons
Declared path parameter "step_uuid" needs to be defined as a path parameter at either the path or operation level
Jump to line 6445
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports/test_cases/{test_case_uuid}/test_case_reasons
Declared path parameter "test_case_uuid" needs to be defined as a path parameter at either the path or operation level
Jump to line 6445
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{node}/comments.post.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/commit/{node}/comments" path
Jump to line 7215
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/log
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 7385
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/log.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/log" path
Jump to line 7410
Semantic error at paths./repositories/{workspace}/{repo_slug}/refs/tags.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/refs/tags" path
Jump to line 7522
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/ssh/key_pair
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 7560
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/ssh/key_pair.put.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/ssh/key_pair" path
Jump to line 7578
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/ssh/key_pair.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/ssh/key_pair" path
Jump to line 7609
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/ssh/key_pair.delete.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/ssh/key_pair" path
Jump to line 7632
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/ssh/known_hosts/
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 7702
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/ssh/known_hosts/.post.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/ssh/known_hosts/" path
Jump to line 7728
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/ssh/known_hosts/.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/ssh/known_hosts/" path
Jump to line 7755
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 8370
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}.put.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}" path
Jump to line 8421
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}" path
Jump to line 8465
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}.delete.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}" path
Jump to line 8497
Semantic error at paths./repositories/{workspace}/{repo_slug}/environments/
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 8731
Semantic error at paths./repositories/{workspace}/{repo_slug}/environments/.post.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/environments/" path
Jump to line 8757
Semantic error at paths./repositories/{workspace}/{repo_slug}/environments/.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/environments/" path
Jump to line 8784
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 9323
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations.post.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations" path
Jump to line 9375
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations" path
Jump to line 9419
Semantic error at paths./snippets/{workspace}/{encoded_id}/{revision}/patch.parameters.1.name
Path parameter "spec" must have the corresponding {spec} segment in the "/snippets/{workspace}/{encoded_id}/{revision}/patch" path
Jump to line 9454
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 9869
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/.post.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines/" path
Jump to line 9895
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines/" path
Jump to line 9922
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/stopPipeline
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 9930
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/stopPipeline.post.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/stopPipeline" path
Jump to line 9950
Semantic error at paths./repositories/{workspace}/{repo_slug}/deployments_config/environments/{environment_uuid}/variables
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 10074
Semantic error at paths./repositories/{workspace}/{repo_slug}/deployments_config/environments/{environment_uuid}/variables.post.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/deployments_config/environments/{environment_uuid}/variables" path
Jump to line 10100
Semantic error at paths./repositories/{workspace}/{repo_slug}/deployments_config/environments/{environment_uuid}/variables.post.parameters.3.name
Path parameter "variable_uuid" must have the corresponding {variable_uuid} segment in the "/repositories/{workspace}/{repo_slug}/deployments_config/environments/{environment_uuid}/variables" path
Jump to line 10115
Semantic error at paths./repositories/{workspace}/{repo_slug}/deployments_config/environments/{environment_uuid}/variables.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/deployments_config/environments/{environment_uuid}/variables" path
Jump to line 10137
Semantic error at paths./repositories/{workspace}/{repo_slug}/refs.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/refs" path
Jump to line 10416
Semantic error at paths./repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments/{comment_id}.put.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments/{comment_id}" path
Jump to line 10568
Semantic error at paths./repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments/{comment_id}.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments/{comment_id}" path
Jump to line 10618
Semantic error at paths./repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments/{comment_id}.delete.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments/{comment_id}" path
Jump to line 10674
Semantic error at paths./repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments.post.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments" path
Jump to line 11001
Semantic error at paths./repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments" path
Jump to line 11063
Semantic error at paths./repositories/{workspace}/{repo_slug}/environments/{environment_uuid}/changes/
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 11400
Semantic error at paths./repositories/{workspace}/{repo_slug}/environments/{environment_uuid}/changes/.post.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/environments/{environment_uuid}/changes/" path
Jump to line 11416
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/variables/{variable_uuid}
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 11623
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/variables/{variable_uuid}.put.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/variables/{variable_uuid}" path
Jump to line 11641
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/variables/{variable_uuid}.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/variables/{variable_uuid}" path
Jump to line 11677
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/variables/{variable_uuid}.delete.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/variables/{variable_uuid}" path
Jump to line 11705
Structural error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/logs/{log_uuid}.get
should have required property 'responses'
missingProperty: responses
Jump to line 11829
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/logs/{log_uuid}
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 11829
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/logs/{log_uuid}
Declared path parameter "repo_slug" needs to be defined as a path parameter at either the path or operation level
Jump to line 11829
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/logs/{log_uuid}
Declared path parameter "pipeline_uuid" needs to be defined as a path parameter at either the path or operation level
Jump to line 11829
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/logs/{log_uuid}
Declared path parameter "step_uuid" needs to be defined as a path parameter at either the path or operation level
Jump to line 11829
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/logs/{log_uuid}
Declared path parameter "log_uuid" needs to be defined as a path parameter at either the path or operation level
Jump to line 11829
Structural error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports/test_cases.get
should have required property 'responses'
missingProperty: responses
Jump to line 11913
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports/test_cases
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 11913
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports/test_cases
Declared path parameter "repo_slug" needs to be defined as a path parameter at either the path or operation level
Jump to line 11913
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports/test_cases
Declared path parameter "pipeline_uuid" needs to be defined as a path parameter at either the path or operation level
Jump to line 11913
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports/test_cases
Declared path parameter "step_uuid" needs to be defined as a path parameter at either the path or operation level
Jump to line 11913
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/ssh/known_hosts/{known_host_uuid}
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 13963
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/ssh/known_hosts/{known_host_uuid}.put.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/ssh/known_hosts/{known_host_uuid}" path
Jump to line 13981
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/ssh/known_hosts/{known_host_uuid}.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/ssh/known_hosts/{known_host_uuid}" path
Jump to line 14017
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/ssh/known_hosts/{known_host_uuid}.delete.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/ssh/known_hosts/{known_host_uuid}" path
Jump to line 14045
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 14136
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}" path
Jump to line 14154
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{commit}/pullrequests
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 15130
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{commit}/pullrequests.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/commit/{commit}/pullrequests" path
Jump to line 15150
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations/{annotationId}
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 15214
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations/{annotationId}.put.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations/{annotationId}" path
Jump to line 15255
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations/{annotationId}.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations/{annotationId}" path
Jump to line 15304
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations/{annotationId}.delete.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations/{annotationId}" path
Jump to line 15341
Semantic error at paths./workspaces/{workspace}/search/code.get.operationId
Operations must have unique operationIds.
Jump to line 15579
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/build_number
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 15709
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/build_number.put.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/build_number" path
Jump to line 15731
Semantic error at paths./repositories/{workspace}/{repo_slug}/deployments/{deployment_uuid}
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 16413
Semantic error at paths./repositories/{workspace}/{repo_slug}/deployments/{deployment_uuid}.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/deployments/{deployment_uuid}" path
Jump to line 16431
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/schedules/
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 16444
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/schedules/.post.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/schedules/" path
Jump to line 16470
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/schedules/.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/schedules/" path
Jump to line 16501
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config
Declared path parameter "workspace" needs to be defined within every operation in the path (missing in "put"), or moved to the path-level parameters object
Jump to line 16651
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config.put.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config" path
Jump to line 16665
Semantic error at paths./repositories/{workspace}/{repo_slug}/deployments/
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 16964
Semantic error at paths./repositories/{workspace}/{repo_slug}/deployments/.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/deployments/" path
Jump to line 16978
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{commit}/reports
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 17014
Semantic error at paths./repositories/{workspace}/{repo_slug}/commit/{commit}/reports.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/commit/{commit}/reports" path
Jump to line 17026
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/variables/
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 17157
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/variables/.post.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/variables/" path
Jump to line 17183
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/variables/.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/variables/" path
Jump to line 17210
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/schedules/{schedule_uuid}
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 17218
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/schedules/{schedule_uuid}.put.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/schedules/{schedule_uuid}" path
Jump to line 17236
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/schedules/{schedule_uuid}.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/schedules/{schedule_uuid}" path
Jump to line 17272
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/schedules/{schedule_uuid}.delete.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/schedules/{schedule_uuid}" path
Jump to line 17300
Semantic error at paths./users/{selected_user}/search/code.get.operationId
Operations must have unique operationIds.
Jump to line 17917
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/schedules/{schedule_uuid}/executions/
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 17918
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/schedules/{schedule_uuid}/executions/
Declared path parameter "schedule_uuid" needs to be defined as a path parameter at either the path or operation level
Jump to line 17918
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines_config/schedules/{schedule_uuid}/executions/.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines_config/schedules/{schedule_uuid}/executions/" path
Jump to line 17936
Semantic error at paths./repositories/{workspace}/{repo_slug}/refs/branches.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/refs/branches" path
Jump to line 18787
Semantic error at paths./repositories/{workspace}/{repo_slug}/deployments_config/environments/{environment_uuid}/variables/{variable_uuid}
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 19354
Semantic error at paths./repositories/{workspace}/{repo_slug}/deployments_config/environments/{environment_uuid}/variables/{variable_uuid}.put.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/deployments_config/environments/{environment_uuid}/variables/{variable_uuid}" path
Jump to line 19372
Semantic error at paths./repositories/{workspace}/{repo_slug}/deployments_config/environments/{environment_uuid}/variables/{variable_uuid}.delete.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/deployments_config/environments/{environment_uuid}/variables/{variable_uuid}" path
Jump to line 19411
Semantic error at paths./users/{username}/ssh-keys/.put.parameters.1.name
Path parameter "key_id" must have the corresponding {key_id} segment in the "/users/{username}/ssh-keys/" path
Jump to line 19492
Semantic error at paths./users/{username}/ssh-keys/.get.parameters.1.name
Path parameter "key_id" must have the corresponding {key_id} segment in the "/users/{username}/ssh-keys/" path
Jump to line 19570
Semantic error at paths./users/{username}/ssh-keys/.delete.parameters.1.name
Path parameter "key_id" must have the corresponding {key_id} segment in the "/users/{username}/ssh-keys/" path
Jump to line 19651
Structural error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports.get
should have required property 'responses'
missingProperty: responses
Jump to line 19659
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 19659
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports
Declared path parameter "repo_slug" needs to be defined as a path parameter at either the path or operation level
Jump to line 19659
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports
Declared path parameter "pipeline_uuid" needs to be defined as a path parameter at either the path or operation level
Jump to line 19659
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/{step_uuid}/test_reports
Declared path parameter "step_uuid" needs to be defined as a path parameter at either the path or operation level
Jump to line 19659
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 21136
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}" path
Jump to line 21154
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 21201
Semantic error at paths./repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/" path
Jump to line 21215
Semantic error at paths./repositories/{workspace}/{repo_slug}/environments/{environment_uuid}
Declared path parameter "workspace" needs to be defined as a path parameter at either the path or operation level
Jump to line 21768
Semantic error at paths./repositories/{workspace}/{repo_slug}/environments/{environment_uuid}.get.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/environments/{environment_uuid}" path
Jump to line 21786
Semantic error at paths./repositories/{workspace}/{repo_slug}/environments/{environment_uuid}.delete.parameters.0.name
Path parameter "username" must have the corresponding {username} segment in the "/repositories/{workspace}/{repo_slug}/environments/{environment_uuid}" path
Jump to line 21814
Semantic error at paths./snippets/{workspace}.get.parameters.1.name
Path parameter "username" must have the corresponding {username} segment in the "/snippets/{workspace}" path
Jump to line 21961

[craftamap]

so, basically the swagger.json of atlassian is invalid. However, you are still possible to click generate client at the top.

[ktrysmt]

Oh, thank you for the info. Let me check...

[ktrysmt]

docker run --rm -it -p 4010:4010 stoplight/prism:3 mock -h 0.0.0.0 https://bitbucket.org/api/swagger.json

or use swagger-go.

[ebh]

I've been really struggling with this 😞

The test in user_test.go works as you know. But I've not been able to work out how to get any of the tests in the other files working. Let me list through what I've found.

• branchrestrictions_test.go - Prism exposes the endpoint http://0.0.0.0:4010/repositories/aut/saepe/branch-restrictions but I cannot work out how to generate a body that Prism will consider valid

• client_test.go - Passes as it does not involve calls to Prism

• diff_test.go - Prism exposes the endpoint http://0.0.0.0:4010/repositories/est/voluptatem/diff/voluptas but it does not return a body and so the test fails

• environment_test.go - Prism only exposes the endpoint http://0.0.0.0:4010/repositories//ut/environments/ which as you can see is not a valid one.

• list_test.go - Prism exposes the endpoint http://0.0.0.0:4010/repositories/perferendis but because of an error in https://bitbucket.org/api/swagger.json Prism returns this error "Your schema contains $ref. You must provide full specification in the third parameter."

• repository_test.go - Prism does not seem to expose an endpoint in the format /repositories/{workspace}/{repo_slug} although it is specified in https://bitbucket.org/api/swagger.json

• workspace_test.go - I can get TestListWorkspaces to successfully make a call to http://0.0.0.0:4010/workspaces. But Prism returns "http://example.com" for the next property. And so when the logic in Client.execute() follows that the test fails.

I considered covering other areas, such as /repositories/{workspace}/{repo_slug}/pipelines/** but they all seem to have issues too.

I suspect that a lot of these errors are due to errors in https://bitbucket.org/api/swagger.json. As you have noted above the file fails validation. I've raised a support ticket with Atlassian about the validation errors.

I also had a bit of play around with other OpenAPI mock servers, to see if they were any better. But I didn't find anything promising.

Not sure how to proceed from here. Do you have any suggestions?

[ebh]

Just an update on this. Bitbucket Support have been back in contact with me. They are actively working on the validation errors in OpenAPI (Swagger) documentation (https://bitbucket.org/api/swagger.json). They have already fixed a number of issues but there are multiple teams involved and so it is taking some time to fix them all. But it is encouraging that they actively working on it, and it is not just sitting in a backlog 😄

[ebh]

Bitbucket Support has provided the following update:

Hi Alex,

Thanks for the wait. The fix might take longer than expected so we decided to create a public bug report on this so you can get updates directly from our developer moving forward.

Please Click This affect my team and Watch the bug report so that you'll be notified when there's an update at:

• https://jira.atlassian.com/browse/BCLOUD-20803

I hope this helps, please let me know if you have any additional questions or issue.

I've marked the BB issue as "This affects my team" as requested and included a comment on the BB issue linking back to this one.

[ktrysmt]

Thanks a lot! @ebh

[maxbrunet]

FYI BCLOUD-17601 has been closed :tada:

Robin Stocker added a comment - 12/Nov/2021 1:45 AM:

The remaining errors have now been fixed!

This returns no errors anymore: https://validator.swagger.io/validator/debug?url=https%3A%2F%2Fapi.bitbucket.org%2Fswagger.json

And swagger-cli is also happy:

$ swagger-cli validate https://api.bitbucket.org/swagger.json
https://api.bitbucket.org/swagger.json is valid

[ktrysmt]

@maxbrunet Really!? Oh, thank you for this.