Jesse Bye

The PR was merged in March. That makes it about 6 months now with no releases. Has this project been abandoned? Is it time to fork and publish our own...

If it helps anyone, I've forked this repo and created a new release that should support SSO: https://github.com/jessebye/amazon-ecr-credential-helper/releases/tag/v0.6.2

@mickmcgrath13 @underrun We've just been testing out deployment of the helm chart in our EKS cluster and encountered this error. I tried to work around it by adjusting the hook...

This is definitely concerning to us. We're trying to adopt Bottlerocket but I'm a bit worried about the interaction with `cluster-autoscaler` as it currently stands: 1. Autoscaler requests a new...

We are seeing this problem as well, using the latest `k8s.helm.v3.Release`. We set `dependencyUpdate: true` but it doesn't appear to run a `helm dep up` prior to the templating, so...

@nitrocode there's a merge conflict, would you mind updating your branch?

@keithduncan @yob anything blocking this? Just curious if this needs changes or is good to ship. > Without lifecycle hooks, I think this PR is highly likely to interrupt running...

I hit this error as well, but with no existing users - after creating a new user, I can't do a grant: ``` data "aws_db_instance" "database" { db_instance_identifier = "${var.db_host}"...

@dtuite sure! Does it make sense to incorporate this functionality into this plugin, or create a new plugin for it? It uses the GraphQL API, not the Rest API, so...

@dtuite Yes, I agree that rewriting existing functionality in GraphQL would be good. I don't really have the bandwidth for that though... I'm happy to share the code I've written...