Ethan Pransky

prepare-response-headers in redirect causes ClassCastException

3

java.lang.ClassCastException: clojure.lang.Keyword cannot be cast to java.lang.String at org.httpkit.HeaderMap.camelCase(HeaderMap.java:77) at org.httpkit.server.HttpHandler.run(RingHandler.java:97) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) This seems to be happening because the headers of...

In the Vault KV Secret Backend, the code was not scanning recursively properly, so only secrets that weren't in nested paths were being imported be Terraformer. This PR fixes this...

Any attributes applied to a TourGuide object which is anchored on a View within a DialogFragment show up below the DialogFragment, thus not achieving the desired effect. I think this...

AWS Secret Backend TTL configs use `/sys/mounts/:path/tune` instead of `/aws/config/lease`

2

The [aws_secret_backend](https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/aws_secret_backend) resource includes [default_lease_ttl_seconds](https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/aws_secret_backend#default_lease_ttl_seconds) and [max_lease_ttl_seconds](https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/aws_secret_backend#max_lease_ttl_seconds). These seem to relate to generic [Mount tuning](https://www.vaultproject.io/api-docs/system/mounts#tune-mount-configuration) instead of the AWS-specific [lease configuration](https://www.vaultproject.io/api-docs/secret/aws#configure-lease). This is fine, but a little misleading. IMHO there...

Not sure why I'm getting this. I'm not a pro with composer, but I included this package like so: "require" : { "prawnsalad/nexmo": "dev-master" } The package gets built in...

Currently: Currently, it looks like the handler reports events using [combined_host_tags](https://github.com/DataDog/chef-handler-datadog/blob/master/lib/chef/handler/datadog_chef_tags.rb#L125) which is a `set of host tags based off the chef run`. It doesn't look like the handler supports...