First set of plugins

[ryanblock]

As requested by @andybee in the Arc / #aws-lite Discord, here's the Architect-centric list of plugins I'm looking at picking off on the way to 1.0. These assume, of course, that we're reasonably happy with the plugin API (see: #14).

Moreover, this list doesn't intend to imply that other plugins folks intend to be published under @aws-lite/* won't be considered or accepted, just that these are the ones we, the maintainers, are likely ourselves to prioritize (namely because they help us migrate away before the Mar 2024 aws-sdk (v2) Lambda deprecation deadline).

Requirements:

• API Gateway v2 (@architect/deploy, @architect/functions)
• DynamoDB (@architect/functions, @architect/sandbox)
• SNS (@architect/functions)
• SQS (@architect/functions)
• SSM (@architect/functions, @architect/deploy, @architect/destroy, @architect/env, @architect/inventory)
  • This will probably be a rare partial implementation to start, as Architect's usage is limited to the Parameter Store

Nice to have:

• CloudFormation (@architect/deploy, @architect/destroy, @architect/logs)
• CloudFront (@architect/deploy)
• CloudWatch Logs (@architect/destroy, @architect/logs)
• Lambda (@architect/deploy)
• S3 (@architect/asap, @architect/deploy, @architect/destroy)
  • This one will likely need some outside help, it's chonky! 😅

[andybee]

Looks good, definitely focussing on the things Architect requires is a good v1 scope definition. I also don't necessarily dislike more being (clearly documented) partials that only tick the Architect dependency boxes to get a v1 out sooner...?

Are we considering any kind of "stake your claim" approach, to avoid 2x people attempting the same one?

[ryanblock]

I'd like to try to avoid partial plug-ins if possible, but I also understand that it's probably going go on a plug-in by plug-in basis. Dynamo for example had a number of very chunky methods, and then dozens of really easy ones that required almost no work at all. If a service API is just nothing but really big, meaty methods, many of which are uncommonly used, it probably makes sense to pick them off over a longer period of time rather than letting the perfect be the enemy of the good.

As for a land grab, while we've definitely seen some initial excitement around this project, I'm doubtful that enough folks are going to be rushing in on plugins to have such conflicts. And if so, I would really rather encourage folks to participate in the spirit of open source and become co-maintainers. That said, if anyone wants to take on some plugins, please do use this thread to state your intentions/link to your PRs, etc!

[andybee]

I'm going to attempt the RDS Data API to dip my toe in as 1) it's small, 2) I have a direct requirement for it.