I have seen other post asking for mutliple API Keys (one per integration) or with finer grain permission. That would be even better, but this request is much more humble, so might be trivial to implement from your R&D.
Agree with GBE and cbn. Our development team is scratching their heads on why this is so different than every other integration. We were told to "have all of the pages open at once" but no system updates instantaneously, so this suggestion does not solve the issue at all. Downtime = lost revenue and frustration for potential and current customers. We now have to wake up in the middle of the night to deploy changes across our entire system as the best attempt at minimizing down time 😞 Please address this!
This is VERY unfortunate as we may end up with gaps in our integration.
Normally you would have a grace period for the old key which would give you e.g. 24 hours to get all related systems updated. We cannot just release a new version and HOPE that nothing happens during the interval from where the key is changed in HubSpot and then it is deployed with our own app.
Please contact me in case you want to know how these things work in the real world and not in your lab. Thanks.