Add jq as an install requirement

[rocketnova]

We originally wanted to keep the installation requirements for platform repos to a minimum. However, as the project has grown, at the current stage of maturity, it would be really useful to include jq as a lightweight dependency for our scripts.

Options to consider:

• We set it as a dependency in the README and, in our instructions, assume that users have jq already installed
• We could explicitly include instructions to install jq as one of the set up instructions, such as in set-up-infrastructure-tools
• We could bundle it into an executable
• We could assume the user has docker installed and run jq inside a docker container

Reference:

• Create more flexible terraform wrapper script #614 (comment)

[rocketnova]

My recommendation:

We set it as a dependency in the README and, in our instructions, assume that users have jq already installed

I think this is the initial lightest weight option. We can always revisit in the future if/when we change the way we handle scripting/template lifecycle management.

[lorenyu]

One of the first two options seems preferable to me.

[KevinJBoyer]

FWIW I think jq is already an implicit dependency, I see it in bin/check-database-roles.sh and create-or-update-database-roles.sh

[rocketnova]

I think that script used in the AWS Lambda, which isn't part of the template scripting run outside of the lambda, such as the install script or the update template script.

[KevinJBoyer]

My understanding is that script runs locally to invoke the AWS Lambda (and jq is part of what's being run locally)

[rocketnova]

@KevinJBoyer Ah thank you. You're correct. We should definitely make the dependency on jq explicit then and we can start using it more liberally in our other scripts.