Getting Value Conversion error when pass "kubernetes" schema from the caller side

[smeeklai]

Hi. I would like to define kubernetes schema on the caller (live) side and pass to the module. However, I got Value Conversion error as shown below:

Error: Value Conversion Error
│
│   with module.flux.provider["registry.terraform.io/fluxcd/flux"],
│   on ../../../modules/flux/main.tf line 19, in provider "flux":
│   19:   kubernetes = var.flux_kubernetes
│
│ An unexpected error was encountered trying to build a value. This is always an error in the provider. Please report the following to the provider developer:
│
│ Received unknown value, however the target type cannot handle unknown values. Use the corresponding `types` package type or a custom type that handles unknown values.
│
│ Path: kubernetes
│ Target Type: *provider.Kubernetes
│ Suggested Type: basetypes.ObjectValue

On the caller side, I declare:

flux_kubernetes = {
  config_path = "~/.kube/config"
  config_context = "docker-desktop"
}

On the module, I do:

provider "flux" {
  kubernetes = var.flux_kubernetes
  ...
}

This is variables.tf

variable "flux_kubernetes" {
  type = any
}

Not sure does this suppose to work or I might miss something?

[phillebaba]

Which version of the provider are you using?

[swade1987]

Hi @smeeklai 👋

I hope you are doing well! As part of our ongoing effort to maintain and improve the quality of our project, I've been reviewing open issues and came across the one you've reported. First off, thank you for taking the time to contribute by reporting this issue; your input is crucial to us.

Upon reviewing the details of your issue, I noticed that it involves the use of a resource or feature that has yet to be supported since the 1.0.0 release of our project, which was approximately 9 months ago. This might be a key factor in the challenges you're experiencing. We understand that changes and deprecations can impact your work, and we're here to help navigate these transitions. If there are specific reasons you've continued using this unsupported resource or if there's any way we can assist in migrating to a supported alternative, please let us know.

Additionally, to ensure the efficient management of our issue tracker and to focus on issues that are actively affecting our community, we have implemented a policy for issues that remain inactive. If there is no activity on this issue within the next 3 weeks, we will consider the issue inactive and close it for you. This doesn't mean your issue is not important to us, but rather that we aim to keep our focus on actively pursued concerns. Of course, if the issue continues or if you have further updates in the future, feel free to reopen the issue or create a new one.

Thank you once again for your contribution to our project. Your feedback not only helps us improve but also supports the broader community in overcoming similar challenges. We look forward to hearing from you and hope to resolve any outstanding concerns together.

Best regards,

Steve