-
Notifications
You must be signed in to change notification settings - Fork 672
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
Error: can not marshal to path in request for field ConfigId. Due to can not marshal a nil pointer #2166
Comments
Thank you for reporting the issue. We have raised an internal ticket to track this. Our service engineers will get back to you. |
The |
Thank you for the response @iliassox This is the Json Response I fetched using API from the browser where it does a GET call to fetch Apdex Thresholds from where I was able to extract the configId and the display name as you cannot access them directly from the OCI console.
And this issue is specific only to Apdex Thresholds, I am able to use terraform for other apmconfig resources like Span Enrichments, Span Filters, Custom Metrics without any issues. And I'm also able to fetch the same data using OCI_CLI Note: I have truncated a few characters in the value of id for security reasons |
Can you try changing your terraform file to have something like this:
Where I was able to reproduce the issue, and this change seems to have worked! |
You can also use a script that creates the config and you use the values from the created resources which also works:
This is from this documentation |
Thanks a lot @iliassox. After trying out the change you suggested, I was able to get the data as output. I actually never came across the format of the configIds in any documentation |
Hi @iliassox, our primary objective was to automate the creation and updating of Apdex Threshold configurations using Terraform. However, we’ve encountered a limitation in OCI where the Apdex ruleset is a singleton and must always be present, causing issues with Terraform as it attempts to create the resource on the first run. Is there a workaround for this? Perhaps by creating a dummy tfstate file to bypass the initial run, or by directly calling the update Apdex API instead of the create API? |
Community Note
Terraform Version and Provider Version
Terraform v1.9.3
on linux_amd64
Affected Resource(s)
Data Source: oci_apm_config_config
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Output with current configuration of the apm_config, in this case Apdex Thresholds
Actual Behavior
Erroring out when taking in the paramter of ConfigId
Steps to Reproduce
terraform plan
Important Factoids
References
Similar to the issue:
#1726
The text was updated successfully, but these errors were encountered: