[Bug][Bitbucket] GET endpoint for Bitbucket scope-configs always fails about incubator-devlake

[dosubot]

The issue you're encountering with the GET endpoint /plugins/jira/connections/{connectionId}/scope-configs/{id} returning a 400 error with the message "missing path variable scopeConfigId" is due to a misinterpretation of the path variable. The correct path variable should be {id}, not {scopeConfigId}.

Steps to Resolve

1. Ensure Correct Path Variable: Make sure that the request URL uses {id} as the path variable, not {scopeConfigId}. The correct URL should be:

   /plugins/jira/connections/{connectionId}/scope-configs/{id}
   

2. Check for Misconfiguration or Bug: If the error message still mentions "missing path variable scopeConfigId", it might be due to a misconfiguration or a bug in the error handling logic. The extractConfigParam function is responsible for extracting and validating the connectionId and id parameters from the path variables. If these parameters are invalid, the function returns an error.

3. Verify Endpoint Configuration: Ensure that the endpoint is correctly configured in the routing setup. The route should be defined as follows:

   // GetScopeConfig return one scope config
   // @Router /plugins/jira/connections/{connectionId}/scope-configs/{id} [GET]
   func GetScopeConfig(input *plugin.ApiResourceInput) (*plugin.ApiResourceOutput, errors.Error) {
       return dsHelper.ScopeConfigApi.GetDetail(input)
   }

Additional Information

• Unit Tests: There are unit tests for the GetScopeConfig endpoint, and they pass successfully. The relevant test is TestCreateScopeConfig, which includes a call to GetScopeConfig to verify the created scope configuration.

• Logging and Debugging: Ensure that logging is enabled to capture more detailed information about the error. Adjust the LOGGING_LEVEL and LOGGING_DIR settings in the configuration file to capture detailed logs.

If the issue persists, it might be helpful to review the middleware or routing configurations that could be affecting the path variable resolution. Additionally, checking for any recent changes or commits in the repository that might have introduced this issue could provide further insights.

Details

Sources

• backend/plugins/jira/api/scope_config_api.go
• backend/test/e2e/remote/python_plugin_test.go
• backend/server/services/remote/plugin/scope_config_api.go
• backend/plugins/jira/impl/impl.go
• config-ui/src/api/plugin/jira/index.ts
• backend/impls/logruslog/init.go
• devops/releases/lake-v0.18.0/env.example
• devops/releases/lake-v0.13.0/env.example
• devops/releases/lake-v0.15.0/env.example
• backend/plugins/tapd/api/scope_config_api.go
• backend/helpers/pluginhelper/api/scope_generic_helper.go
• backend/plugins/github/api/scope_config_api.go
• backend/plugins/azuredevops_go/api/scope_config_api.go

About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

[klesh]

Fixed by #7498