RFC: Spike Serverless plugin thinking

[72636c]

This is by no means ready to merge, but I'm keen to get feedback on the approach.

The alternative would be for us to run the CDK synth offline and hardcode the CloudFormation resources that we inject rather than relying on CDK to generate them dynamically. This may mean that we'd need to implement our own logic around generating unique CloudFormation resource names (assuming that the current approach exercises CDK name generation in a deterministic fashion 🤔).

---

E: I'm yet to look at how event source mappings & permissions are updated, so that may end up increasing the effort.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c493faa

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[AaronMoat]

I'm not super familiar with some of this, but in the interests of unblocking ✅ in case you don't get any other feedback, as I don't see anything wrong.

The high level approach seems sane.

The installation/setup instructions could probably be replicated to the package's README so that it appears in the NPM package's page.