Revision pinning provides the flexibility to accept changes when it is safe to do so, and also to avoid them during critical periods. For example, you can use revision pinning to turn off dynamic reactivations during a sales event or code freeze.
You can also perform these tasks using the EdgeWorkers API.
This example shows how the CoreSite dev team can pin revision
2-2 to prevent updates during a site wide sale.
- Select the revision that you want to pin from the list available on the Revisions tab.
- Click the Pin revision button to disable dynamic reactivation. This revision,
2-2, will remain active even if new versions of the child EdgeWorkers are activated.
You can only pin the revision ID that is currently active.
During the sale the Security dev team continues to work on updates to their EdgeWorker.
When they activate version
7 of the Security EdgeWorker the parent, CoreSite, isn’t dynamically reactivated because it’s pinned.
We can see that the Security EdgeWorker continues to use version
We can also confirm that the version number of the Security EdgeWorker is
6 by reviewing the
bundle.json file in the combined code bundle.
7 has been activated on the network but does not trigger a dynamic reactivation of the pinned parent EdgeWorker.
To unpin the revision, select it and click the Unpin revision button
Once the revision is unpinned, version
7 of the Security EdgeWorker will trigger a new Revision for the parent EdgeWorker, CoreSite.
To confirm that this Reactivation occurred go to the list of Revisions for the CoreSite EdgeWorker.
You can confirm that version
7 of the Security EdgeWorker appears in the BOM.
Updated about 1 month ago