You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scenario: I have a private Habitat depot where I want to publish my application, acme/myapp. This application is written in Ruby on Rails, and I want to use the core packages as dependencies without rebuilding them or mirroring the public depot to my internal one. I'm okay with my application nodes talking to the public depot, so I would like to use it as a fallback for any packages that can't be found locally.
I propose adding a command-line option to hab pkg install that will use a fallback URL as the depot for missing packages. This option would have a corresponding ENV variable so it wouldn't need to be specified. So for example, if I do:
It would download acme/myapp from my private depot, private-depot.example.com/v1/depot, and any dependencies such as core/ruby or core/glibc from willem.habitat.sh/v1/depot.
I think the "sane default" is for this fallback URL to use the public depot. Perhaps a CLI option and ENV variable to disable this for air-gapped environments that can't talk to the internet.
There will certainly come a point where we're going to need to answer this use-case. For now we're going to flag this as help wanted as we have some other work that would supersede being able to start on this.
The text was updated successfully, but these errors were encountered:
We are actively working on officially supported on-prem depots right now. That work is happening here. That is a private repo for now, but will most likely be open-sourced at some point. Additionally, there is work in progress here to support pulling packages from an upstream depot if your default depot doesn't contain said packages. Both of those should address this issue.
@jtimberman commented on Fri Apr 07 2017
Scenario: I have a private Habitat depot where I want to publish my application,
acme/myapp
. This application is written in Ruby on Rails, and I want to use thecore
packages as dependencies without rebuilding them or mirroring the public depot to my internal one. I'm okay with my application nodes talking to the public depot, so I would like to use it as a fallback for any packages that can't be found locally.I propose adding a command-line option to
hab pkg install
that will use a fallback URL as the depot for missing packages. This option would have a corresponding ENV variable so it wouldn't need to be specified. So for example, if I do:It would download
acme/myapp
from my private depot,private-depot.example.com/v1/depot
, and any dependencies such ascore/ruby
orcore/glibc
fromwillem.habitat.sh/v1/depot
.I think the "sane default" is for this fallback URL to use the public depot. Perhaps a CLI option and ENV variable to disable this for air-gapped environments that can't talk to the internet.
@jtimberman commented on Fri Apr 07 2017
Longer term we will want to implement "pull through proxy" and federation to replace this, but this is fine for an initial spike.
@eeyun commented on Tue Apr 11 2017
There will certainly come a point where we're going to need to answer this use-case. For now we're going to flag this as help wanted as we have some other work that would supersede being able to start on this.
The text was updated successfully, but these errors were encountered: