Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Sunsetting DEPNotify integration #41
I'd like to sunset DEPNotify integration for a few reasons:
If you object with this, please comment and we can discuss. I will leave this open for a week or two and then pull the integration, unless I am convinced otherwise.
In place will be some example scripts that an admin can use and recommended approaches for the JSON.
Those reasons sound pretty solid to me. I'm pretty sure I hit a few of those edge cases while building out our workflows.
With DEPNotify being integrated with NoMAD Login, IAs probably would have needed significant code changes to support that, too. I agree that it's best to separate out the DEPNotify support, since IAs is flexible enough to allow me to build out what I need on my own (that said, I appreciate the example code
referenced this issue
Jan 31, 2019
Just yesterday I was thinking through following problem.
As a result some package from
This thread actually gave me right idea. I need my own LaunchAgents which if going to be part of bootstrap package along with DEPNotify.
Ripping out the code responsible for launching DEPNotify is OK imo. But it still may be good to retain capability to easily write status updates to DEPNotify control file about what installapplications is currently doing. Alternatively we would have to simple shell script for that after every package install.