Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iidy fails to run if .aws directory or profile does not exist #17

Closed
rymndhng opened this issue Nov 22, 2017 · 0 comments
Closed

iidy fails to run if .aws directory or profile does not exist #17

rymndhng opened this issue Nov 22, 2017 · 0 comments

Comments

@rymndhng
Copy link
Contributor

rymndhng commented Nov 22, 2017

iidy should be able to run using only the AWS_* env vars.

For example, if the .aws folder does not exist, it should not fail.

(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: ENOENT: no such file or directory, open '/root/.aws/credentials'
1) If you want to compile the package/file into executable, please pay attention to compilation warnings and specify a literal in 'require' call. 2) If you don't want to compile the package/file into executable and want to 'require' it from filesystem (likely plugin), specify an absolute path in 'require' call using process.cwd() or process.execPath.
(node:1) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
@rymndhng rymndhng changed the title iidy fails to run if .aws/config file does not exist iidy fails to run if .aws directory or profile does not exist Nov 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant