thanks for reporting, will be implemented within this month ;)

when deploying a package that is changing some configuration of ResourceResolverFactory then AEM may restart many bundles and become unstable for a longer time. but... this usually is a one-time situation for the first package deployment. maybe config activation could be smart that activates depending on the first or next package deployment?

thinking about sth like that:

then such foo pkg settings will be automatically in-use basing on path pattern and the fact if package was deployed before or not, AEM_INSTANCE_CHECK_PACKAGE=foo sh aemw pkg deploy --url ... will activate the settings explicitly

@tomasz-sobczyk-wttech , @maciej-majchrzak-wttech WDYT?

or maybe just there should be 2 different done_thresholds

done_threshold: 
   first: 5
   next: 2

This first config is very confusing for me. Why it's even needed? Ideally, I'd like to specify three types of checks:

1. generic check - if AEM is stable, could be used regardless of package installation in any cases by calling aemw instance await
2. default package installation check - to check if instance is stable after installation. It should be possible to completely ignore stability check after installation, so that we don't need to wait until all events stopped processing. This would be useful in a scenario of installing more packages at once. In this case, one could install packages one after another and in the end of the process call the aemw instance await. Additionally, in case of problematic packages they could use the third types of check, which is...
3. specific package installation check - something like you propose with the pattern. done_threshold configuration is fine here.

regarding second point - will be addressed by #159
generic check will have a form of current configuration/options that AEMC gives currently;
third point is a thing to address here / missing feature that we are planning to implement. I guess within next weeks I will find some time to have it done.