Using stack to get around upstream bugs

Recently I bumped into a bug in amazonka.¹ I can't really sit around waiting for Amazon to fix it, and then for amazonka to use the fixed documentation to generate the code and make another release.

Luckily stack contains features that make it fairly simple to work around this bug until it's properly fixed. Here's how.

1. Put the upstream code in a git repository of your own. In my case I simply forked the amazonka repository on github (my fork is here).
2. Fix the bug and commit the change. My change to amazonka-codepipeline was simply to remove the missing fields – it was easier than trying to make them optional (i.e. wrapping them in =Maybe=s).
3. Tell slack to use the code from your modified git repository. In my case I added the following to my slack.yaml:

extra-deps:
  - github: magthe/amazonka
    commit: 1543b65e3a8b692aa9038ada68aaed9967752983
    subdirs:
      - amazonka-codepipeline

That's it!