chore: add sonarcloud properties file

[kim-tsao]

Description

Now that Sonarcloud is enabled, we should set the analysis scope and exclude test files from source scanning in order to reduce the noise.

Which issue(s) does this PR fix or relate to

• Fixes #issue_number
  https://issues.redhat.com/browse/RHIDP-11062

PR acceptance criteria

• Tests
• Documentation

How to test changes / Special notes to the reviewer

[rhdh-qodo-merge]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🔒 No security concerns identified

⚡ Recommended focus areas for review Possible Misconfiguration Using both sonar.sources = . and sonar.tests = . points tests and sources to the same root, relying solely on inclusions/exclusions to separate them. This can lead to double counting or misclassification, especially if patterns miss some files. Consider scoping sonar.sources to non-test dirs and sonar.tests to explicit test dirs. sonar.sources = . sonar.tests= . # Include test subdirectories in test scope sonar.test.inclusions = tests/**/*, integration_tests/**/*, **/*_test.go # Exclude test subdirectories from source scope sonar.exclusions = tests/**/*, integration_tests/**/*, **/*_test.go Glob Patterns The glob **/*_test.go appears in both test inclusions and source exclusions. Ensure this matches your language mix; for non-Go projects it’s unnecessary, and for multi-language repos you might also need patterns for other test conventions (e.g., **/*.spec.ts, **/*Test.java). Validate that the patterns are correct and exhaustive. sonar.test.inclusions = tests/**/*, integration_tests/**/*, **/*_test.go # Exclude test subdirectories from source scope sonar.exclusions = tests/**/*, integration_tests/**/*, **/*_test.go

📄 References redhat-developer/rhdh-operator/best_practices.md [116-165] redhat-developer/rhdh-operator/best_practices.md [110-115] redhat-developer/rhdh-operator/README.md [78-84] redhat-developer/rhdh-operator/README.md [74-77] redhat-developer/rhdh-operator/examples/rhdh-cr.yaml [5-30] redhat-developer/rhdh-operator/docs/orchestrator.md [164-243] redhat-developer/rhdh-operator/docs/orchestrator-cicd.md [221-232] redhat-developer/rhdh-operator/config/profile/rhdh/default-config/deployment.yaml [74-82]

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rhdh-qodo-merge]

PR Type

Enhancement

---

Description

• Add SonarCloud configuration file to define analysis scope

• Exclude test files from source scanning to reduce noise

• Include test directories in dedicated test scope

---

File Walkthrough

Relevant files

Configuration changes

.sonarcloud.properties Configure SonarCloud analysis scope and exclusions              .sonarcloud.properties Created new SonarCloud configuration file with analysis scope settings Configured source and test scopes to include all directories Defined test file inclusions for tests/, integration_tests/, and *_test.go patterns Excluded test files from source scope to prevent duplication and reduce analysis noise +9/-0

---

[rhdh-qodo-merge]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Remove redundant test file exclusion Remove the redundant sonar.exclusions property. Files specified in sonar.test.inclusions are automatically excluded from source analysis, so this explicit exclusion is unnecessary. .sonarcloud.properties [5-9] # Include test subdirectories in test scope sonar.test.inclusions = tests/**/*, integration_tests/**/*, **/*_test.go -# Exclude test subdirectories from source scope -sonar.exclusions = tests/**/*, integration_tests/**/*, **/*_test.go - Apply / Chat Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies that sonar.exclusions is redundant because files matched by sonar.test.inclusions are automatically excluded from source analysis, thus simplifying the configuration and improving maintainability.	Low
Organization best practice	Clarify analysis scope intent Clarify intent in comments to explain that tests are analyzed but not counted as sources due to explicit inclusions/exclusions, preventing confusion. .sonarcloud.properties [1-3] -# add test files to analysis scope +# Analyze entire repo but treat tests as tests only (see inclusions/exclusions below) sonar.sources = . -sonar.tests= . +sonar.tests = . Apply / Chat Suggestion importance[1-10]: 6 __ Why: Relevant best practice - Keep documentation synchronized with implementation changes, specifying scope and behavior to avoid user confusion when behavior evolves.	Low
More

[rm3l]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rm3l

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rm3l]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment