hook. With the
hookin place, the DCD will work fully automatically:
Supernova Cloud > Code Integration > Hooks. To create a new hook, simply click on
+ NEWbutton to show the configuration dialog.
notify, which is optional (but highly recommended):
namerepresents human-readable name of the hook so you know what is what
design systemrepresents a single design system that will be watched
eventrepresents the event upon which this hook will be called
exporterrepresents exporter which will run when the event happens
notify(optional) represents API URL which should be called when hook finishes
confirm. If you want to disable the hook, you must delete it using the appropriate option in the hook detail. Lastly, the hook can be updated at any moment just by reconfiguring their properties. Please note that any modification to the hook will be immediately applied and used on the next run.
notifyshould be left empty. This will create a build for each run and will keep it securely stored on our servers until you want to access the code.
notifyURL which will point to your API that will manage the incoming data.
notifyset, every time the exporter runs (either successfully or with potential error), we will invoke your API and send the following JSON payload through
iduniquely identifies the job / exporter run inside your workspace
statusresults either to
logsgive you full log of exporter run, using Pulsar logging engine
urlswill be provided as well. At this point, there will always be just one link, but we are reserving this option for more flexibility down the road.
.zipfile that can only be accessed with the URL provided in the payload, containing the structured output of the exporter.