Brett cave

You could generate a key pair on every server and agent, as well as accept the fingerprint... or you could provision the agents / server config files using shared configs...

@Sigularusrex try using `kind = Kind.find_by(:name => "author")` instead of `.where` - it will return the correct object type that has an `id` attribute. #78 has been submitted to resolve...

> > > This is still happening with Terraform 0.13.5, when using `body` with [an API Gateway (v2)](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/apigatewayv2_api#body), using version 3.14.1 of the AWS provider. > > To add more...

After testing some variations on this, the issue can be easily replicated. In Mongo 2.4, the introduction of roles allows certain roles to only be created in the "admin" database...

As a workaround, if you're using a driver or connection that doesn't support database switching, you can switch will `getSiblingDB` ``` mongo -u admin -p adminpass admin --eval "db.getSiblingDB('otherDb').collection.count()" ```

The issue at opening is referenced, but locked - this is a duplicate, but with a workable approach.

Hi Andreas, thanks, I have a better understanding of what is happening now. The issue relates to permissions / accessing the USB device. I don't have a udev service in...

the changes don't allow pipelining to the cluster: redisCluster.pipeline { p=> // execute redis commands }

I am not sure if it should select any node, each command in the pipeline should use the same method for finding a node that the cluster would use for...

On another note, we are using redis cluster for HA, not only for performance / scaling, so any write operation is run with cluster.onAllConns, while read operations are invoked directly,...