Yun Zhi Lin

started working on this in https://github.com/yunspace/serverless-golang/tree/dynamo

I followed the above instructions with `AWS_SDK_LOAD_CONFIG=1` using `credential_process` method with `aws-sso-util`. However it appears that the AWS CLI completely ignores the `credential process` as per this issue here: https://github.com/aws-amplify/amplify-cli/issues/6882

Ok I figured out the issue. For this `credential_process` to work, all of the following conditions must be met: - Set `AWS_SDK_LOAD_CONFIG=1` - Set `AWS_Profile={your profile}` - Run `amplify init`...

Yes that would be handy, applies to Docker also. We currently specify 4 ENV variables for DB... pain...

@niwinz I noticed you have written a lot custom code with the async sockets. Have you ever considered using `java.nio.channels` which uses `epoll` under the hood? It also automatically defaults...

also `xnio` switches between `kqueue`, `epoll` etc under the hood depending on the OS: https://github.com/xnio/xnio/blob/588aa2f9fb0d7e613dcfc036982c2e0cb40b05c9/nio-impl/src/main/java/org/xnio/nio/NioXnio.java

Podman and Buildah are drop in, daemonless replacements for docker CLI. There is no need for Kubernetes nor DinD. Any standard linux runner will do. In reference to the original...

@gzoller take a look at https://github.com/frol/docker-alpine-oraclejdk8

@kdvolder thanks for looking into this. Who should I raise the issue with for Gradle Tooling API?

hi @oillio I think it may be possible in #46 to squash everything after bf0197755e0c682cbfe320270fe2bd6ddce2f817 because all the commits are authored by you. having been a major culprit in making...