Alex Romanov

I hit this bug yesterday when I tried to add the plugin. Came to almost the same concussion - in my case the variable is named `AWS_REGION`. I guess both...

Same for me... it works fine yesterday, but now it's clear screen. I tried to set 256Mi - same story :-( 512Mi did the trick. But 512 seems too much,...

Got same error here's my docker-compose file ``` mysql: image: sameersbn/mysql environment: - DB_USER=db - DB_PASS=db - DB_NAME=db ``` root@pass:/opt/teampass# docker-compose up mysql Recreating teampass_mysql_1 Attaching to teampass_mysql_1 mysql_1 |...

:+1:

Any chance this can be pushed further?

I don't think it's related to module, as I have just got the same error without using modules. I switched away from ``` repository = data.helm_repository.reponame.metadata[0].name ``` to a direct...

I did run `helm repo update` and then `terraform apply` again - the issue has gone. So it most certainly is related to the abovementioned issue. Thanks!

I got into this again. Apparently, I have a subdirectory named `flux` in the directory with the rest of the terraform files. And helm_release named `flux` as well. So I...

You can use just the ENV variables, I don't have config file at all. ``` export SEAL_ORGANISATION="org" export GITHUB_MEMBERS="user1,user2,netflash" export SLACK_CHANNEL="#channel-name" export DYNO=true ```

I have it. I use it. Not ready for merging yet. I can polish it a little bit today and create a PR for review.