[Bug] "payload encoding is not supported" when Temporal CLI is using a codec for encryption

[bchav]

What are you really trying to do?

I was setting metadata to 'temporal.io/ignore-last-modifier="true"' but my controller was still not rolling out new versions.

Error log: "unable to get Temporal worker deployment state: unable to decode metadata payload for key temporal.io/ignore-last-modifier: encoding binary/encrypted: payload encoding is not supported

[DonForbes]

I guess two things from my perspective

1. Should this metadata be encrypted and if so can the controller support the encryption?
2. Useful to have in the trouble shooting section that the controller will fail to rollout a new version if the temporal.io/ignore-last-midifier has been set using a codec services in the CLI.

[Shivs11]

Thanks for opening this issue folks. Not sure if we do have immediate plans of supporting encoding within our metadata fields when using the controller. FWIW and if you wanted to get things moving, this does work when JSON is passed along via the CLI.

Shall discuss internally and post updates here.

[carlydf]

Solution: Document that you should not encrypt your metadata when you set this field