community-plugins icon indicating copy to clipboard operation
community-plugins copied to clipboard

🐛 Sonarqube: The url /api/sonarqube/findings?componentKey= deprecated

Open glopezGitHub opened this issue 1 year ago • 2 comments

Plugin Name

SonarQube

📜 Description

The Sonarqube Enterprise Edition v10.6 the URI /api/sonarqube/findings?componentKey= respond {"msg":"Unknown url : /api/sonarqube/findings"

This version uses the uri api/projects/export_findings?componentKey

👍 Expected behavior

we can configure the api uri in order to inyect the api value

sonarqube: baseUrl: ${SONARQUBE_BASEURL} externalBaseUrl: ${SONARQUBE_BASEURL} apiKey: ${SONARQUBE_APIKEY} api: findingsUrl: api/projects/export_findings?project=

👎 Actual Behavior with Screenshots

image

curl --header 'Authorization: Bearer sqa_xxxx ' 'https://xxx.xxxx.xxxx/api/sonarqube/findings?componentKey=xxxx' {"errors":[{"msg":"Unknown url : /api/sonarqube/findings"}]}[

curl --header 'Authorization: Bearer xxxxx' 'https://xxx.xxx.xxx/api/projects/export_findings?project=xxxxx {"export_findings": [stanceKey='''''' {"key":"xxxxxxxxxxxx","projectKey":"xxxxxxxx",xxxxx}

👟 Reproduction steps

1- Configure Sonarquebe Plugin 2 - Configure Sonarqube Catalog

📃 Provide the context for the Bug.

The tab SonarQube Code Quality No information to display

👀 Have you spent some time to check if this bug has been raised before?

  • [X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

Are you willing to submit PR?

None

glopezGitHub avatar Aug 29 '24 10:08 glopezGitHub

@punkle ^ FYI

nickboldt avatar Sep 24 '24 15:09 nickboldt

@glopezGitHub I tried to repro this issue, and I could not... here is what I did:

Ran this:

docker run --name sonarqube-custom -p 9000:9000 sonarqube:10.6-enterprise

  • I logged into port 9000
  • I created a project
  • I created a user api key

I edited the app-config.yaml file here workspaces/sonarqube/app-config.yaml to add this.

sonarqube:
  baseUrl: ${SONARQUBE_BASE_URL}
  apiKey: ${SONARQUBE_API_KEY}

I edited the file workspaces/sonarqube/examples/entities.yaml to set the sonarqube.org/project-key of the backstage component to my project key that I created earlier.

Then I set the environment variables: SONARQUBE_BASE_URL to 'http://localhost:9000' and the SONARQUBE_API_KEY to the api key I created.

Then I ran the dev script from this file workspaces/sonarqube/package.json

I could see this:

image

And the network response from findings returned a 200 status code:

image

Can you help me with more info to understand the issue better?

punkle avatar Oct 07 '24 09:10 punkle

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Dec 06 '24 12:12 github-actions[bot]