Janos

This may have to be an optionally enabled feature since the cardinality can explode if many different backends are used.

I have no strong opinion, labels, commands in comments, anything works for me as long as we don't need to do the backport manually. In the past I used work...

@kishaningithub not in this case because we are only backporting PRs that have been added to OpenTofu in the first place. We are not backporting Terraform PRs this way.

Hi @dannyibishev both of the requested files are available [in the release](https://github.com/opentofu/opentofu/releases/tag/v1.6.0). However, I'd heavily assume that they would expect the binary to be called `terraform` instead of `tofu`, so...

@dannyibishev Terraform is a registered trademark of HashiCorp. We do not intend to be distributing any packages, binaries or aliases named `terraform` in them as part of OpenTofu releases. While...

I just managed to read through the RFC and I have one question/addition. I think it would be beneficial to separate the encryption keys and encryption methods. The reasoning would...

Hi @sandstrom currently only full encryption will be implemented, additional modes would be something to add at a later stage.

Hey @nneul we have published a video containing an updated syntax on how it will work here: https://www.youtube.com/watch?v=rR4IbhlRSkI Additionally, we have an updated technical description here: https://github.com/opentofu/opentofu/blob/main/docs/state_encryption.md I believe this...

@skeggse unfortunately, this is impossible. The provider needs the original value in cleartext to do its work. The protocol isn't designed to work without the cleartext values.

Correct, and provider authors would be forced to pick either Terraform or OpenTofu to support, which is not ideal.