{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/d6b8061648bb4b9fb2afc5142d340537\" frameborder=\"0\" width=\"1664\" height=\"1248\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1248,"width":1664,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1248,"thumbnail_width":1664,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/d6b8061648bb4b9fb2afc5142d340537-00001.gif","duration":349.36666666666713,"title":"Harness Service Hooks 🎣","description":"Hey there! I wanted to share some exciting news about our new feature called Service Hooks. With Service Hooks, users can extend certain functionalities when we perform a Kubernetes or native Helm deployment. This feature allows users to fetch files, template manifests, and check for steady state. We've had customers using Helm plugins, customized plugins, and generated their own custom templating binaries that generate manifest for them. With Service Hooks, users can inject certain actions into our deployment, and we support various action types. We have a pre-hook and a post-hook, which means after performing a specific action, we can run a set of logic. We also support various plugins, such as the SOPS plugin and the Helm secrets plugin, which allows users to configure a SOPS key, use a decrypted YAML, and render in the secret. This feature is behind a feature flag, and we had a few customers who requested this capability. Check it out and let us know what you think!"}