YAML not working about stormpath-node-config HOT 7 CLOSED

Hi Radley,

Thanks for reporting this.

I have looked into it and I don't see any issue with the first thing that you mentioned. Binding there seems fine. But the second one was clearly wrong and the expanded home directory wasn't even used. So even though we expanded it, we were still used the original path.

I have fixed this and will soon create a PR for review/release.

A quick question, what OS are you using?

from stormpath-node-config.

Im using OSX El Capitan 10.11.2

I also pulled down the new file and tried using it. I'm still getting an error that API key ID and secret is required. I have put some logs in checking the state of the original file path and the expanded file path. Here are their results:

original: ~/.stormpath/stormpath.json
expanded: /Users/MY_USERNAME/.stormpath/stormpath.json
original: ~/.stormpath/stormpath.yml
expanded: /Users/MY_USERNAME/.stormpath/stormpath.yml
original: /Users/MY_USERNAME/workspace/MY_APP/stormpath.json
expanded: /Users/MY_USERNAME/workspace/MY_APP/stormpath.json
original: /Users/MY_USERNAME/workspace/MY_APP/stormpath.yml 
expanded: /Users/MY_USERNAME/workspace/MY_APP/stormpath.yml

currently my YAML file resides here /Users/MY_USERNAME/workspace/MY_APP/stormpath.yml. (which would show that the final instance of the expandedDir being correct.)

Could multiple trips through the process be affecting the result?
I get that it's going through the various steps in checking where the file could be located, I'm just wondering.

side note: I've tried saving it as both .yaml and .yml file, neither are working

from stormpath-node-config.

I am noticing that the strategies are called with a config parameter, but this seems to be just a default object. Like when ValidateClientConfigStrategy is called, it has a fleshed out object, but the values like client.apiKey are null

from stormpath-node-config.

Nvm, it works thanks!

from stormpath-node-config.

Did you get it to work? Was it because of permissions to the file?

from stormpath-node-config.

It's working. I wrote the yaml without spaces between the colon and the value so it was getting parsed incorrectly. Really sorry about this. :\

from stormpath-node-config.

No problem! Good to hear that you solved it! :) Closing this issue now.

from stormpath-node-config.