generate event for sns about new put event in S3 -- bug/example

[awsdocs]

generate event for sns about new put event in S3 -- bug/example

[dancaspi]

So.. at least for me, the issue was solved by using a bit of sed, but i think it should be fixed somehow (or i am missing something). the problem turns out to be twofold: the message is in fact a string, so that's ok. but it needs to be completely escaped to be json: once for quotation marks and once for newlines. the eventual solution that worked for me was:

sam local generate-event sns notification --message "$(sam local generate-event s3 put --bucket yourbucket --key your/file/key.txt | sed 's/\"/\\"/g' | sed -E ':a;N;$!ba;s/\r{0,1}\n/\\n/g')" > s3_put_event_via_sns_notification.json

and so you will have a json that properly serves as input for local run of SAM and parses correctly. Am I missing something? I am running version SAM CLI 0.47.0

should this be closed?

[joshbean]

Closing this issue or pull request in advance of archiving this repo. For more information about the decision to archive this repo (and others in the "awsdocs" org), see the announcement on the AWS News Blog.