We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Bug Report
After installing the dependency into the project all invokes show
Running "serverless" from node_modules
This causes an issue with the AWS Profile being loaded
In the Yaml: profile: profile2
profile: profile2
Profile 2 appears to be "loaded" but when you check the Credential token using
AWS.config.getCredentials(function (err) { if (err) console.log(err.stack); // credentials not loaded else { console.log("Access key:", AWS.config.credentials.accessKeyId); } });
It returns the "default" AWS token. This causes a whole bunch of errors within a project that works perfectly without the plugin.
Removing the plugin fixes these issues.
The text was updated successfully, but these errors were encountered:
I forked a version of this without the serverless Peer-dependency in the package.json and this issue was resolved.
Maybe something to look into? https://github.com/mofolo/serverless-step-functions-without-serverless
Sorry, something went wrong.
No branches or pull requests
This is a (Bug Report / Feature Proposal)
Bug Report
Description
After installing the dependency into the project all invokes show
Running "serverless" from node_modules
This causes an issue with the AWS Profile being loaded
In the Yaml:
profile: profile2
Profile 2 appears to be "loaded" but when you check the Credential token using
It returns the "default" AWS token.
This causes a whole bunch of errors within a project that works perfectly without the plugin.
Removing the plugin fixes these issues.
Additional Data
Framework Core: 3.26.0 (local) 3.7.1 (global)
Plugin: 6.2.2
SDK: 4.3.2
3.11.1
The text was updated successfully, but these errors were encountered: