Adam Fisher

This is still an issue and I'd add that the current approach relies on deprecated constructors in the SDK. The deprecation means that my workaround above no longer works if...

My goal is to be able to use provider chains to authenticate AWScala's functionality. With that in mind I've created [a branch that lets developers use AWS providers to authenticate...

:+1: Might be helpful to log the ARNs of any resources that get created. Better still, make it easy to read that into a script that wraps the AWS CLI...

After writing this it occurred to me to configure the plugin to use the bare command names, rather than qualified paths to the elm executables. This works, but the `You...

If you've a pointer for me about how to retrieve the full, resolved list of dependencies I'll be happy to give it a crack.

Since circe `0.14.3` I'm seeing version conflict errors between circe `0.13.0` (pulled in by this library) and `0.14.x` from the rest of the ecosystem. I'm not sure what it is...

I'm sure a post-merge hook wouldn't do what people expect. Let's chat about it IRL, after stand up?

This would be great, but for it to work circe would need to move to a `1.x` release. Version schemes typically treat `0.x` versions as "development", so the standard rules...

Version 0.14.x of circe is backwards-binary-compatible with 0.13.x versions, as you'd expect for a minor change in a mature library, but as you might not expect for a pre-release minor...

The trouble is that right now the ecosystem [depends](https://github.com/circe/circe-derivation/issues/346#issuecomment-910219725) on compatibility between `0.13.x` and `0.14.x` but adding a `versionScheme` would explicitly instruct tools to consider these as incompatible. As far...