Closed 9numbernine9 closed 5 months ago
I was just about to create a new issue when I found this one and I encountered exactly the same bug on my side.
Good job opening this issue!
@9numbernine9 Thanks for the report! May I ask how is your provider configured? Can you share a sample of your configuration that includes the provider
block?
@alexhung For sure! It's configured thusly:
provider "platform" {
url = data.terraform_remote_state.workloads.outputs.jfrog.artifactory_url
access_token = jsondecode(data.aws_secretsmanager_secret_version.artifactory.secret_string)["terraform_access_token"]
}
Artifactory itself is deployed in a separate repo, hence the usage of remote_state
to get the URL.
1.7.1
working perfectly - thanks @alexhung !
Describe the bug Greetings!
After upgrading to version
1.7.0
of theplatform
provider we're seeing a stack trace from the provider during the plan phase. This happens even when just targeting the apply to a single resource within theplatform
provider.Sample
main.tf
:Our Artifactory is self-hosted and deployed to EKS. This behaviour does not occur when using version
1.6.0
of theplatform
provider.7.77.9
1.8.0
1.7.5
but the behaviour is the same.terraform-provider-platform
version:1.7.0
1.6.0
Requirements for and issue
curl
it at$host/artifactory/api/system/version
Expected behavior The provider should not crash. :smile:
Additional context N/A