better process error handling

This fixes a bug where if an uncaught exception was encountered during request processing, the server would hang until timeout.

New Logging paradigm

This incorporates the FINTOJS_LOG_PATH environment variable for better use with sudo and npm. See the synopsis for more details.

1.1.2

This release forces 2.68.* version of the SDK for sigv4 compatibility

Minor change to intsallFintorc.js

This will check to see if any roles are set up for you from all_accounts.json. If not it will crash since that state is not really acceptable and will preserve any existing fintorc file.

Issue #13 fix and other improvements

Changelog:

1. Use Temporary creds instead of STS directly. This allows for proper refresh tracking of the assume role session since AWS.TemporaryCredentials uses STS.assumeRole() under the hood.
2. Fixed the Credential chain provider configs to have a better sense of this this wouldn't be an issue if I did this in ECMA 6
3. configure master AWS.Config object with proper chained credentials

Issue 11 Fix

This release has a bug where assumed role sessions get lost..
see issue 13 for more info. This is fixed in version 1.1.0.

First Alpha release

Change log

• Addressed issue #2

Issue #6 fix and other fixes.

This fixes Issue 6 and adds documentation for testing.
Change-Log

• Added a check for trailing '/' as that is not a valid REST endpoint
• updated README.md to include npm commands for startup and testing
• added documentation for test script

Controller Beta

moved much of the controller action to a separate controller class and cleaned up a lot of code.

I also added tests which I will document in a later release.

DO NOT USE WITH AWS CLI

Unfortunately, AWS CLI doesn't follow REST implementation all that well, I think, and tries to hit /latest/meta-data/iam/security-credentials/ instead of /latest/meta-data/iam/security-credentials which causes this server to get a key for the default role (which I think is how it should work, IMO) and crashes the cli client which isn't expecting json as output (which I think is incorrect, IMO, AWS CLI should be smarter).

see issue 6 for more info. A fix is forthcoming.

Better error handling

• better error handling for when AWS SDK throws and error during processing.