Hi all! Reminder that the monthly Pants developer meeting is tomorrow (Monday) at 1 PM PST, as a huddle in this channel (#C0D7TNJHL). This is where we discuss the development roadmap for Pants, and all are welcome to join, whether to participate or to lurk! DM me if you have any items to add to the agenda.

I would like to get to one of these at some point but won't be able to make the one today, so I'll just post my question async here. Myself and a few others and have all taken stabs at trying to build

keyring

integration into Pants. For my particular use case, I need this done in such a way that it works within both local and docker environments. I've opened a draft PR following @fast-nail-55400 suggestion of executing

keyring

locally once per session when needed, storing the credentials in the cache (I'm like 95% sure the code in my draft PR will need more tinkering to work with

docker_environment

still though), and then just having a script that echos them when needed. However, the storing them in cache part feels very hacky to me the way it's currently written. Curious if you or anyone else had any thoughts or opinions around this. My 2 cents is that it would be great to have a standardized mechanism for storing stateful values between pants invocations.

I should be able to attend to discuss https://github.com/pantsbuild/pants/pull/22243 live if you think that would be helpful @broad-processor-92400 , otherwise we can keep the discussion on the pr.

On the suggested topics front: I didn't get to participate, but maybe a call-by-name week retro?