| set -euo pipefail | |
| CLUSTER="${1}" | |
| TASKS="${2}" | |
| aws ecs describe-tasks --cluster "${CLUSTER}" --tasks "${TASKS}" \ | |
| | jq '.tasks[] | |
| | { | |
| meta: { | |
| clusterArn: .clusterArn, |
| """ | |
| A sketch of a django-redis integration with the Redis cluster features recently added to | |
| https://github.com/redis/redis-py from https://github.com/Grokzen/redis-py-cluster | |
| For non-clustered Redis, django-redis's ConnectionFactory does some management of | |
| connection pools shared between client instances. | |
| The cluster client in redis-py doesn't accept a connection pool from outside, they're | |
| managed internally. To support that, we won't be caching connection pools and passing | |
| them into clients, we will instead be caching client instances. |
Some commands for use in Circle CI config related to the task of getting GitHub's SSH keys into your known_hosts file.
Why is that useful? It's useful to me because I have some Circle
CI jobs where I create a new branch, push it back to GitHub and
create a PR. Without having a github.com entry in your known_hosts
file, the git push would fail. I mean, really it would hang
waiting for user input with a prompt like:
