Clickpipe Buildkite Error: Value Conversion Error

[PondiLogeswari]

We are having a build failure with the below error, however there was no change to Clickpipe as part of the build.

Note : The clickpipes are in 'continuous' ingestion mode and both the clickpipes are getting the same error.

Error: Value Conversion Error with clickhouse_clickpipe.clickpipe-rta-employee-demographic-assignments_CD4A65AF (clickpipe-rta-employee-demographic-assignments/clickpipe-rta-employee-demographic-assignments), 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 correspondingtypes package type or a custom type that handles unknown values. │ │ Path: │ Target Type: models.ClickPipeScalingModel Suggested Type: basetypes.ObjectValue

[jkaflik]

@PondiLogeswari could you please provide details about our issue:

• provider version
• reproducible TF code

This will help us troubleshoot this issue. Thanks

[davidwheeler123]

Hey @jkaflik I'm on the same team as @PondiLogeswari - we're using 3.6.3-alpha2

I'll see if we can get a reproducible case shortly

[tpanetti]

Hey @jkaflik I'm on the same team as @PondiLogeswari - we're using 3.6.3-alpha2

I'll see if we can get a reproducible case shortly

Thanks David! We made changes to the scaling conversion logic in the latest release. Let us know if it's reproducible on 3.7.0-alpha1.

[davidwheeler123]

OK will give it a try. The other thing is that it's proposing these changes to the clickpipe

development-clickhouse-clickpipe-rta-employees    # clickhouse_clickpipe.clickpipe-rta-employees_C755608E (clickpipe-rta-employees/clickpipe-rta-employees) will be updated in-place
                                                  ~ resource "clickhouse_clickpipe" "clickpipe-rta-employees_C755608E" {
                                                        id             = "de5cfbb6-a4ac-419c-859f-2bb0ab5cad0e"
                                                        name           = "employees"
                                                      ~ scaling        = {
                                                          ~ replica_cpu_millicores = 125 -> (known after apply)
                                                          ~ replica_memory_gb      = 0.5 -> (known after apply)
                                                          + replicas               = (known after apply)
                                                        } -> (known after apply)
                                                        # (5 unchanged attributes hidden)
                                                    }

                                                Plan: 0 to add, 1 to change, 0 to destroy.

We don't set scaling at all so it shouldn't be updating it, IIUC

[tpanetti]

OK will give it a try. The other thing is that it's proposing these changes to the clickpipe

development-clickhouse-clickpipe-rta-employees    # clickhouse_clickpipe.clickpipe-rta-employees_C755608E (clickpipe-rta-employees/clickpipe-rta-employees) will be updated in-place
                                                  ~ resource "clickhouse_clickpipe" "clickpipe-rta-employees_C755608E" {
                                                        id             = "de5cfbb6-a4ac-419c-859f-2bb0ab5cad0e"
                                                        name           = "employees"
                                                      ~ scaling        = {
                                                          ~ replica_cpu_millicores = 125 -> (known after apply)
                                                          ~ replica_memory_gb      = 0.5 -> (known after apply)
                                                          + replicas               = (known after apply)
                                                        } -> (known after apply)
                                                        # (5 unchanged attributes hidden)
                                                    }

                                                Plan: 0 to add, 1 to change, 0 to destroy.

We don't set scaling at all so it shouldn't be updating it, IIUC

Ah will take a look at not including this info in the plan at all to avoid confusion, this is the lowest and default scaling option so the same as not specifying scaling at all.

[davidwheeler123]

3.7.0-alpha1 works, thanks