Post deploy hook about bref

[mnapoli]

Most of the time a post-deploy hook doesn't make sense on FaaS because the lambda's filesystem is readonly and the rest (/tmp) can contain temporary files but those are lost on next executions.

If you need to generate a cache it's usually better to generate it before deploying?

[t-geindre]

You're right about the file system.
But that's still relevant for a Redis cache for instance.

[mnapoli]

OK I see, in that case you could do the operation manually right? That would look something like this:

bref deploy
bref cli -- cache:warmup-redis # this runs on a prod lambda

(or use a script/Makefile that wraps the 2)

I think for now it might be better to not add a post-deploy hook because it can be very confusing to users (since it doesn't work like most other hosting solutions). And since it's easily doable outside of Bref it's not a huge necessity either (Bref doesn't intend to cover everything in deployment, other tools can compliment it). Maybe in the future that could change but at first I'd rather aim to have as few features as possible that are not related to FaaS/serverless stuff.

[t-geindre]

Actually, that's exactly what I was thinking after posting my last message.
Since we already use Makefile to run our deployments, we can add more tasks after bref deploy.