Adding encryption example using a KMS and JWT-based auth

[phillipskevin]

No description provided.

[CLAassistant]

All committers have signed the CLA.

[cretz]

Thanks! Added some review comments. Also may want to poe format and poe lint-types. Also may need to sign the CLI. Feel free to add a test or two, but not required.

[phillipskevin]

Thanks @cretz for all of the great feedback. I'll make these updates in the next day or two and will let you know!

[phillipskevin]

Thanks for all the suggestions, @cretz. I think I've addressed everything. Let me know if you have any more feedback.

[cretz]

Make need to run poe lint to confirm type checking.

[phillipskevin]

Should be good to go now, @cretz. Thanks again!

[cretz]

@phillipskevin - Looks like there's a type error. Specifically, since we allow our Python samples to run in in all non-EOL Python versions, you have to change things like tuple[bytes, bytes] to typing.Tuple[bytes, bytes] for 3.8 to work.

For this error:

Library stubs not installed for "requests" (or incompatible with Python 3.8)

You may need to add a dependency for https://pypi.org/project/types-requests. Have not investigated this.

[phillipskevin]

Looks like CI is still failing after adding the types-requests dependency. I'll try to look into why.

[cretz]

Looks like it's still complaining on 3.8. I admittedly have not spent time digging into this.

[phillipskevin]

Python 3.8 went end of life last week, so having some trouble testing it now. Will the versions used in CI be updated? Or will you continue to support 3.8 for some time?

[cretz]

I suspect we will EOL it too soon, though no specific timeline. EDIT: Opened temporalio/sdk-python#672 for dropping 3.8 support.

[dlee-bitovi]

Hey @cretz , Happy Friday!

Here's some screenshots of my recent commits to this PR that successfully run the below commands locally - would you be willing to approve the workflows to run (when you get a chance)?

1. uv sync
2. poe lint
3. poe test

Thanks!

[cretz]

Approved to run CI now, thanks for sticking with this! Also, if possible, any kind of tests to confirm this remains working would be helpful (we have had some contributed samples become stale and stop working for one reason or another).

[Mattchewone]

Do we need to expose the encode over http?

[cretz]

It's a good idea to. Our web UI and CLI use the encode side when you are starting workflows, sending queries, etc from those interfaces.

[cretz]

If possible, any tests would help here, though I know it can be a bit difficult since the cloud JWKS is hardcoded. We can discuss merging without tests if they are too hard to write or they need to be done after merge. (we know many of our samples like the encryption sample don't have tests and we keep getting burned by not having them)