Azure / Azure/azure-quickstart-templates
Sonarqube templates
- Dominant language
- Bicep
- Stars
- 14.9k
- Forks
- 16.2k
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 6
Description
--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------
Sorry to hear you had a bad experience with one of the templates :worried: But, in case you're just asking a question, we're happy to help. You can also check if the question might already have been asked here https://github.com/Azure/azure-quickstart-templates/issues?utf8=%E2%9C%93&q=is%3Aissue
We've created an outline of recommended sections to fill out that will help make this Pull Request awesome!
--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------
Concerning the templates prefixed by:
**"Sonarqube Docker Web App"**
### Issue Details
The environment variables should be prefixed by SONAR_ and not SONARQUBE_ for the docker container to recognize them with current image builds/labels (9.x or lts).
Using host storage or an azure file share to persist the local "/opt/sonarqube/conf" folder allows to host a "sonar.properties" text file in which you may add the line:
```
sonar.search.javaAdditionalOpts=-Dnode.store.allow_mmap=false
```
Which makes the solution fully functional, once again, with images above version 7.8.
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the templates prefixed "Sonarqube Docker Web App" and inspect their container environment-variable definitions and storage configuration. Verify the current SonarQube image requirements for SONAR_ variables and the sonar.properties setting, then confirm the affected templates deploy with the corrected configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, docker
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100