Closed kyleawayan closed 3 years ago
I think this is fixed in master, via https://github.com/dancrumb/generator-serverless-policy/pull/35 - but there hasn't been a release with the latest changes.
@dancrumb can we cut a new release?
in the mean time, for everyone else, you can get the fixes by installing the master branch:
$ npm install generator-serverless-policy@dancrumb/generator-serverless-policy#master
Hey folks,
I'm on vacation until Friday, so I'll get to this next week.
Also, if anyone is interested in helping maintain this repo, please open an issue and we can discuss.
Thanks
Dan
On Tue, Aug 3, 2021, 11:51 Ryan Rhee @.***> wrote:
in the mean time, for everyone else, you can get the fixes by installing the master branch:
$ npm install @.***/generator-serverless-policy#master
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dancrumb/generator-serverless-policy/issues/63#issuecomment-892003876, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABWCT2FDAVDZGAIIQWNFGLT3ANBLANCNFSM4VCD3E4A .
Hey folks;
Sorry - moving house, kids back to school, etc. etc.
v3.1.2 is now released so closing this issue
After generating a policy with S3 enabled, I tried to deploy the hello-world example for Severless. Serverless said
I had to manually edit the policy on the AWS console and allow it. It worked after.
By the way, I'm new to Serverless. The first time I ran the generator, I disabled S3 access since I plan not to use S3 for the Serverless function. It looks like Serverless needs it regardless to upload the files. I'm not sure if that should be a default option or not.
Thanks though for making this!