UAAS-583 - Events to hook into on transfer

Created by gardarth 29 Sep 2017, 15:06:37 Updated by Mikulas Tomanka 18 Oct 2017, 12:52:30


In our solution we have our own cache mechanism for ecommerce solution. The client works with all content on DEV and then transfers it to LIVE.

We need to reset the cache for the node that has been transferred but at the moment we know only of an hack that will trigger an event after transfer and we do not know what nodes have been transferred so we need to clear the cache for all the products in the site. That is to expansive for us.

Events like these would really help bigger sites to work with the Cloud.


Mikulas Tomanka 02 Oct 2017, 08:39:17

Hi we have just finished working on a post deployment webhook feature which would let you know exactly which files have changed in a particular deployment. Is this what you're looking for? If so this should be rolled out this Tuseday 3/10/17.

gardarth 02 Oct 2017, 09:21:26

@Mikulas Yes that could work, where can I approach information on the webhook ? Will the information be out on tuesday also ?

Mikulas Tomanka 02 Oct 2017, 12:32:40

Hi We're working on the documentation as of right now. Currently the documention is in a feature-deploymentWebhook branch @ and will be later under UmbracoCloud->Deployment->Webhook when merged with master branch.

gardarth 05 Oct 2017, 13:41:03

Thank you this looks good. Will try it soon. @Mikulas

Mikulas Tomanka 05 Oct 2017, 17:52:29

I'll be closing this then. Hope you find this usable :).

gardarth 18 Oct 2017, 12:27:50

Hi Mikulas,

I think we closed the issue to soon. Webhooks is not the solution for the problem as it only gives us events when code has been deployed. What I need is an event when content has been transferred between environments.

For examples I would like to get list of nodes that were transferred from dev to live.


Mikulas Tomanka 18 Oct 2017, 12:52:30

Hello I've reopened this now. Thanks again for getting back to me.

Note for self: This will have to be handled by Deploy internally as that is what deals with content transfers.

Priority: Normal

Type: Feature (request)

State: Open




Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version:


Story Points: