New sonarqube_application resource, applications in portfolios, and fixes for permissions on large templates, portfolios on Data Center Edition, and template permissions on Community Build 26.9. No breaking changes.
Features
- feat: add sonarqube_application resource by @Cesarsk in #417 — manages SonarQube applications (Developer edition and above): name, description, visibility, tags and member projects; fixes #385
- feat: let sonarqube_portfolio include applications by @Cesarsk in #423 — new
applicationsargument adds applications to a portfolio, whatever itsselection_mode. Thesonarqube_portfoliodata source now exposesapplicationsandselected_projects
resource "sonarqube_application" "payments" {
key = "payments"
name = "Payments"
projects = [sonarqube_project.api.project, sonarqube_project.ui.project]
}
resource "sonarqube_portfolio" "finance" {
key = "finance"
name = "Finance"
selection_mode = "NONE"
applications = [sonarqube_application.payments.key]
}Fixes
- fix: read every page when sonarqube_permissions looks up a user or group by @Cesarsk in #419 — on a template or project with more than 100 groups or users, a principal beyond the first page was treated as missing, which caused "Provider produced inconsistent result after apply"
- fix: allow portfolios when the edition is spelled "Datacenter", in #423 — portfolios were refused on Data Center Edition whenever the edition was reported or configured as
Datacenter - fix: the sonarqube_portfolio data source no longer crashes on a portfolio in MANUAL mode, in #423 (
Invalid address to set: []string{"selected_projects"}) - fix: ignore template permissions SonarQube cannot manage by @Cesarsk in #426 — Community Build 26.9 lists
architectureadminon permission templates but rejects it on add and remove, so every apply ofsonarqube_permissionson a template failed trying to remove it