Provide ability for administrators to opt-out of auto-updates

[caspiano]

A flow along the lines of...

1. something is broken
2. debug
3. have no idea what's going wrong
4. check discord, there's been a new release
5. apply changes to custom client

has happened to my team and I on 2 occasions now :slightly_frowning_face:

The ideal experience would be a cloudformation variable to specify whether you want to receive auto-updates or not.

Thanks to the whole team for your efforts in developing this platform :dizzy:

┆Issue is synchronized with this Jira Task

[jordyhenry]

I'm highly interested in this feature as well.

Still haven't been through this situation, but I have a large online event planned for December/2020, and our team is working on some custom code for Hubs Cloud, and we were concerned about an update during the event days, that may cause a conflict and we wont have the able time to fix it, as the event will be already running.

So this is a must have feature, so we can plan our deploys and customizations with stable versions in mind. This surely will make this amazing platform even better.

[robinkwilson]

Related + discusses specifics of what would need to be done: https://github.com/mozilla/hubs-cloud/issues/33

[misslivirose]

From #33: Proposed mechanism for pausing updates:

Go to admin console, get a magic value that encodes the current version information of all habitat packages
Go to stack, paste magic value and do a stack update
Roll the nodes
Nodes bootstrap script now defers to magic value to determine version to run
This requires a new AMI bootstrap build which does not have channel bindings burned in

[vhelin]

HI guys!

We at Softability Oy have a big customer who is using Mozilla Hubs that we modified, and currently an auto update means that we'll have to reupload some files to the server, otherwise our mods go missing. Thus we really hope that this feature request gets implemented as soon as possible. :)