Open ParsonsProjects opened 1 year ago
I'm also running into this issue, which has actually been addressed in #536.
The above change hasn't been released yet but you can get around it by pinning the plugin against the latest commit in master
in your package.json
:
"serverless-step-functions": "serverless-operations/serverless-step-functions#42bd42350c33c418762bff6f75cb8b2d6e2d3729"
I tried above configuration with valid=false
. SLS file is not generating the IAM policies required to download the file from s3 bucket. Any suggestion for fixing that?
encountered the same issue as well :(
This is fixed in the latest release! You can try and leave feedback.
@akshaydk
For a non-distributed map (INLINE
), I was receiving the above error on the last release, but that seems to be resolved now. Unfortunately, though I'm now receiving this:
✖ Stack env-my-map-step-function failed to deploy (65s)
Environment: darwin, node 16.18.0, framework 3.26.0 (local), plugin 6.2.2, SDK 4.3.2
Credentials: Local, environment variables
Docs: docs.serverless.com
Support: forum.serverless.com
Bugs: github.com/serverless/serverless/issues
Error:
UPDATE_FAILED: FeatureDashmyDashmapDashfunctionRole (AWS::IAM::Role)
The policy failed legacy parsing (Service: AmazonIdentityManagement; Status Code: 400; Error Code: MalformedPolicyDocument; Request ID: 578bcbb5-63be-4ec6-b2f6-7b6783a479eb; Proxy: null)
If a separate issue needs to be filed, please let me know and I'll do so.
Edit: Looks like this is actually a result of this bug that was filed almost 3 years ago
@cwardcode I tried to reproduce with INLINE
mode, but everything seems fine with the latest version. Good to raise a separate issue with some details so I can help you.
This is a Bug Report
Description
What went wrong?
When using the DISTRIBUTED mode for a Map state the following error is thrown from compileIamRole.js.
What did you expect should have happened?
Serverless file deploys correctly.
What was the config you used?
What stacktrace or error message from your provider did you see?
Additional Data
Solution
There is a very simple solution for this, updating the switch case for Map to use either Iterator or ItemProcessor