Best practice on how to use in Amplify Console build process

[houmark]

Hi there,

Thanks a lot for this. This really should be part of Amplify core, but until then, this plugin has worked very well for us for about a month.

The biggest issue for us was figuring out how we install this package in the build process without installing our entire package.json which includes all our frontend packages.

We did a --no-save in the preBuild process and that worked without issues for a month or so, then just suddenly out of the blue it failed today.

How are you doing this? What's the cleanest way to do this where we are not spending build time on installing more than needed while still getting this package installed? If you have the golden solution here, then I would thank you by adding it to the README as a PR for this repository so others may have an easier time getting it set up. At the same time I may also add a bit of a Q&A that explains how DynamoDB reacts and handles this stuff.

[flogy]

Hi @houmark

Thanks for your request.

About the first part, I personally really just install it in the package.json as explained in the README. Therefore I don't have a solution ready for this. But once you or somebody else finds a solution I'd love to include it in the docs of this directive. I'll therefore leave this issue open for now.

About the seconds part how this directive works behind the scenes, I've now linked the AWS docs about the DeletionPolicy in the README. Hope this helps 🙂