Steve Buikhuizen

same for basic-credentials-provider blocked me. I'm one of those confused people. my workaround is to use jet in shell to assume role and change env vars, then call bb

Thanks for the link but the example is very complex. That will keep me staying with my shell/jet workaround because it's much simpler. sts assume-role is an AWS security best...

happy to. it would take 2 changes: 1. basic-credentials-provider needs a new passthrough arg for aws session token. this is required for assumed roles 2. a new credentials fn that...

fwiw here's my jet-based workaround... ``` - bash /tmp/creds.edn - export AWS_ACCESS_KEY_ID=$(cat /tmp/creds.edn| jet --query ":Credentials :AccessKeyId println") - export AWS_SECRET_ACCESS_KEY=$(cat /tmp/creds.edn| jet --query ":Credentials :SecretAccessKey println") # must include...

the excluded code could also be highlighted in the html with a new toggle i.e. when on, all non-excluded cells become mostly transparent, making it easy to spot the offending...

The commit selection fn can be implemented as a multi-method with a CLI arg to select it. this allows a couple of includes strategies (last-N and last-N-days) but allows projects...

clicks on the legend could also trigger the top level zoom

using Cursive debugger shows that.... malli.core/-set-entries at line 393 has a schema with no -options it was called from malli.utils/assoc where the schema was added somehow the options are being...

I found a workaround by avoid mu/assoc so low priority for me now maybe still useful to know about edge case bugs

already done as a VF component. Should wait on Lightning until it can be used in a normal org (currently DE only) It's a good learning exercise but cannot be...