[Feature] support before and after hook, after call import map deployer

[vctqs1]

In my purpose, after cal imd i'd like to call to another service to update version. and make sure that it also put in lock to handle race-conditional

The behavior look like this

1. use curl call to imd
2. open lock
3. beforeHook
4. update import-map.json file
5. afterHook. that maybe integrate to send noti to slack or another service
6. close lock
7. exec next call

Could the team help to review this, I'd be happy to open PR and contribute if possible

[nhumrich]

Is there a particular reason why these things would have to happen while the manifest is locked vs just doing them out-of-band in your CI/script?

[vctqs1]

Is there a particular reason why these things would have to happen while the manifest is locked vs just doing them out-of-band in your CI/script?

I'd like to store each version of manifest with our service and database. that act looks like a dashboard for deployment. For EX: if we'd like to rollback or check the version causing a bug at cross-team feature, the specific version of team A. you will easy to know the version at that time of other teams also

If it exec out of manifest lock it hard to control transactions and race-condition. for EX: next in the above scenario. in case this is out of the band in CI/scripts. it can't be correct to order of versioning manifest.

• We trigger manifestV1 and V2
• manifestV1 in lock
• manifestV1 unlock -> call update manifest (but might it will take a time)
• manifestV2 in lock
• manifestV2 unlock
• manifestV2 call and finish update extra script
• after that manifestV2 finish update extra script

so in db right now the order looks like

• manifestV2 at 10:00AM
• manifestV1 at 10:02 AM

[vctqs1]

ah nvm I thnk we can use writeManifest https://github.com/single-spa/import-map-deployer/blob/ad02a26b2c7b6bb82425ea39ec4b4a53e5d09f3a/src/modify.js#L69