First, it adds the ability to provide a JSON object as AWSConfigJSON in lieu of providing a path of a JSON configuration file. This works well for dynamic configurations without needed to maintain multiple JSON configuration files for minor AWS configuration changes.
Second, it fixes Issue #14 and allows a hashKey to be set. It defaults to "id".
ca98am79
commented
8 years ago
This pull request is two-fold.
First, it adds the ability to provide a JSON object as
AWSConfigJSONin lieu of providing a path of a JSON configuration file. This works well for dynamic configurations without needed to maintain multiple JSON configuration files for minor AWS configuration changes.Second, it fixes Issue #14 and allows a
hashKeyto be set. It defaults to "id".