Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to reference existing quality profile using data.sonarqube_qualityprofile #235

Open
mikerodionov opened this issue Jan 11, 2024 · 2 comments

Comments

@mikerodionov
Copy link

Hi there,

Thank you for opening an issue.

Terraform Version

terraform -v output below

Terraform v1.6.6
on linux_amd64

  • provider registry.terraform.io/hashicorp/azuread v2.47.0
  • provider registry.terraform.io/hashicorp/azurerm v3.86.0
  • provider registry.terraform.io/jdamata/sonarqube v0.16.10

Affected Resource(s)

Please list the resources as a list, for example:

  • data.sonarqube_qualityprofile

Terraform Configuration Files

data "sonarqube_qualityprofile" "main" {
  name     = "example"
}

Expected Behavior

Provider should look up for existing profile by its name.

Actual Behavior

Terraform returns an error below - it looks like provider looks for project instead of quality profile (though putting into data block name value name of existing project does not change error).

Error: resourceSonarqubeQualityProfileRead: Failed to find project: example

Steps to Reproduce

Just try to use aforementioned data resource and runterraform apply

References

n/a

@edwinvandewerf
Copy link

Hello,

I'm running into the same issue. If you try to refer to a resource instead of data with an existing quality profile the project association is going to fail, although it is probably not intended to use it that way.

@ivanthejedy
Copy link

Seems like this message is copy-paste. The project, rules, profiles, etc fails with the same message:
search over the code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants