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

Topic updates - message.timestamp.*.max.ms not working #445

Open
gautam-goudar opened this issue Sep 24, 2024 · 4 comments
Open

Topic updates - message.timestamp.*.max.ms not working #445

gautam-goudar opened this issue Sep 24, 2024 · 4 comments
Labels
question Further information is requested

Comments

@gautam-goudar
Copy link

Terraform docs say the below topic properties are supported for updates

message.timestamp.before.max.ms
message.timestamp.after.max.ms

However when I try to update my topic with the configs, I get the below error

"message.timestamp.before.max.ms" topic setting is read-only and cannot be updated. Read https://registry.terraform.io/providers/confluentinc/confluent/latest/docs/resources/confluent_kafka_topic for more details.

"message.timestamp.after.max.ms" topic setting is read-only and cannot be updated. Read https://registry.terraform.io/providers/confluentinc/confluent/latest/docs/resources/confluent_kafka_topic for more details.

I see this happening only on our PROD cluster topic and not on the DEV cluster topic, where the properties can be updated using Terraform. The clusters are 100% identical when it comes to settings.

Any help to resolve this would be appreciated.

Thanks

@linouk23
Copy link
Contributor

@gautam-goudar thanks for creating this issue! Could you confirm the version of TF Provider you're using? Based on git blame (link), it should work for all v1.57.0+ versions of TF Provider for Confluent, thank you!

@linouk23 linouk23 added the question Further information is requested label Oct 22, 2024
@gautam-goudar
Copy link
Author

We are using v1.39.0 for the TF provider.

With this version, it works for one environment but fails in other environment. This is the confusion we are having.

@linouk23
Copy link
Contributor

linouk23 commented Oct 22, 2024

@gautam-goudar that sounds interesting that it somehow did work for v1.39.0 as well! Could you update it to v1.57.0+ and try again?

@linouk23
Copy link
Contributor

@gautam-goudar could you take a look at the suggestion above? Thank you!

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

No branches or pull requests

2 participants