Open qubitrenegade opened 5 years ago
This is an interesting one indeed. We actually had behavior like you're describing above for a many months and ended up ripping it all out for a few different reasons. I'm not certain if the plan going forward is to add behavior like this back to the on-prem-depot or not. I think it's something we probably need to discuss with @chefsalim @dmccown and Phil Prasek. For now i'm going to add the needs discussion label to this and we'll revisit it next week when theyre all back!
Haha. You know, I was having a case of Deja Vu when writing this post, but I couldn't find anything in the docs mentioning this functionality so I figured I must be imagining things. Thanks confirming at least this doesn't mean I'm crazy...
;)
On Tue, Feb 19, 2019, 12:14 Ian Henry notifications@github.com wrote:
This is an interesting one indeed. We actually had behavior like you're describing above for a many months and ended up ripping it all out for a few different reasons. I'm not certain if the plan going forward is to add behavior like this back to the on-prem-depot or not. I think it's something we probably need to discuss with @chefsalim https://github.com/chefsalim @dmccown https://github.com/dmccown and Phil Prasek. For now i'm going to add the needs discussion label to this and we'll revisit it next week when theyre all back!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/habitat-sh/on-prem-builder/issues/128#issuecomment-465270789, or mute the thread https://github.com/notifications/unsubscribe-auth/AOQTiYKiFVrAVXOdMPOcLj_xrNcWMIB8ks5vPE0NgaJpZM4a-dZq .
It would be really nice if your on-prem-builder could automatically reach out to the public builder and pull in any requisite packages a la AptCacherNG.
There would probably need to be some guardrails to ensure packages aren't autoupdated "accidentally".
I think this would eliminate the issues I've been running into with the outdated bootstrap bundle.
Thoughts?