We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The TF stack currently relies on local execution of https://github.com/ExpediaGroup/apiary-data-lake/blob/master/scripts/mysql-user.sh which relies on local availability of aws, mysql, and jq executables.
aws
mysql
jq
This could be replaced by use of https://www.terraform.io/docs/providers/aws/d/secretsmanager_secret_version.html for AWS secret retrieval, and https://www.terraform.io/docs/providers/mysql/index.html for interacting with MySQL.
The text was updated successfully, but these errors were encountered:
How much of an issue is this? Could we get a PR? I'm just trying to clean up issues which have been open for months with no movement on them.
Sorry, something went wrong.
It is definitely a stumbling block to using the module... maybe we can at least doc it in the README for now?
Here's a PR that updates the README (Ignore the "Issue 17" bit, I grabbed the wrong issue number): #139
No branches or pull requests
The TF stack currently relies on local execution of https://github.com/ExpediaGroup/apiary-data-lake/blob/master/scripts/mysql-user.sh which relies on local availability of
aws
,mysql
, andjq
executables.This could be replaced by use of https://www.terraform.io/docs/providers/aws/d/secretsmanager_secret_version.html for AWS secret retrieval, and https://www.terraform.io/docs/providers/mysql/index.html for interacting with MySQL.
The text was updated successfully, but these errors were encountered: