This is something I have wanted for a long time: the ability to see deployment logs and inspect what was run. Fortunately, by storing the output of scripts when they finish, I was finally able to implement this feature.
When a deployment is triggered, a script runs on the remote server to start the deployment process. It also makes a callback to Fuse to inform that the script task has finished. Fuse then stores an action to be run after the script completes.
When a deployment is triggered, a script runs on the remote server to start the deployment process. It also makes a callback to Fuse to inform that the script task has finished. Fuse then stores an action to be run after the script completes.
The post-deployment action updates the deployment status. During this step, I take the output of the script task and store it as the output for the deployment. That’s it—super simple.
Next, I had to update the user experience. This time, I wanted to use a modal to display the deployment log instead of creating a new page. Flux made this easy with a flyout modal for showing the deployment logs. Of course, I also ensured that only users with the right permissions can view the deployment log.
I hope you find this feature as helpful as I do.
I hope you find this feature as helpful as I do.