Konstantinos Livieratos
Konstantinos Livieratos
@riontric @romanlobai @Sharlie89 I have two potential ideas for this issue: 1. It might be caused of the build arch of the image 2. It might be related to the...
> @koslib guys this is HUGE. please fix this bug ASAP @SaharAvr We are not a company, I am a person :) Since I also saw (and kept a copy...
> @koslib It was removed because for some reason I mistaken this to be an AWS repo, in which case I wouldn't have removed my original comment > > Now...
@Sharlie89 well, I think I understand what's up - let me explain and please let me know if this makes any sense to you too: - I issued version `v1.25.3`...
@Sharlie89 I was actually wrong. Turns out the issue has to do with the `[email protected]` version, as k8s upgraded the auth api and the token given from that aws cli...
I'm trying to piggy back on your train of thought @Sharlie89 . - `2.0` brought the `sops` executable in the base image, and this is the last image known to...
So the `master` branch works for you but not the `experimental` one. Does this also mean tag `v1.25.4` works? 🤔 Now I'm getting more confused :D But I'll try to...
Hello @jcputter, can you post the snippet which shows how this action is used and the env keys/values provided?
@jcputter I have almost identical setups and it works for me. Can I propose two ideas to try out? 1. Stick to the same setup however pin the action's version...
Hello, thanks for letting me know! Would you like to submit a PR for this? Otherwise I'll fix it as soon as possible!