Janos Miko

When you want to format a timestamp which contains offset: ``` sub("(?.*)\\.[\\d]{3}(?.*)"; "\(.time)\(.tz)") ``` This will transform the following: `2015-03-05T23:51:47.487Z` to `2015-03-05T23:51:47Z` And will work with this as well: `2015-03-05T23:51:47.487+0100`...

+1 for this feature. Could someone verify and accept this PR?

+1, it's kinda annoying :(

+1

I was able to make it work using these values in argo-workflows helm chart: ``` executor: image: registry: quay.io repository: argoproj/argoexec tag: "v3.3.9" ```

I created a PR that should (hopefully) make it possible. https://github.com/bsm/redislock/pull/51

+1 for any of these. It would be really useful if we could manipulate lifecycle rules via variables or dynamic blocks.

You can also give https://github.com/rewardenv/reward a try. It's Warden rewritten in Golang. Find the complete documentation here: https://rewardenv.readthedocs.io

@timo-klarshift you can use my [fork](https://github.com/janosmiko/redislock). Instead of the regular Obtain, call it like this: ``` // Try to obtain lock. locker.Obtain(ctx, "my-key", 150*time.Millisecond, &redislock.Options{ Secret: "test", }) ``` If...

I tried to explain my use case in the PR. But here's a pretty simple one: - Application A is running in a Kubernetes pod, and obtains lock for a...