What were you trying to do that didn't work?

It appears that there is no argument validation when passing arguments to TPM2, e.g.:

# echo "HELLO" | clevis encrypt tpm2 '{"pcrs_ids":"7"}'
... some result ...

Here above "pcrs_ids" was used instead of "pcr_ids".
This may be problematic when binding LUKS devices against TPM2, because the binding will occur but sooner or later, on TPM content change, it's very probable that unlocking won't occur anymore.

What is the impact of this issue to you?

Potential issues in the future

Please provide the package NVR for which the bug is seen:

clevis-15-15.el8
clevis-20-200.el9

How reproducible is this bug?:

Always, see above