Support Private Registries

[jamesbeedy]

I seem to be blocked here due to the fact that my interfaces and layers live in private repositories, and are not on interfaces.juju.solutions.

Request for charm build to support private interface registries.

[ktsakalozos]

A way to hack around your private interfaces is to go and clone them in the JUJU_REPOSITORY used during build:
https://github.com/juju-solutions/layer-cwr/blob/master/templates/BuildMyCharm/config.xml#L59

Although private layer and interface registries is a valid request it will cause fragmentation in the ecosystem. Why don't you share your interfaces with the rest of the world? You do not have to answer I am sure you have your reasons.

[jamesbeedy]

@ktsakalozos thanks for the workaround and response here. The layers and interfaces I have developed to deploy our applications are considered to be private IP of our company. I have been instructed not to share them 😥

On the bright side, I have developed all supporting/intermediary layers and interfaces that are not specific to our applications on my public github under GPL licenses, with entries on the public interfaces registry😀

On fragmentation, possibly it's a good thing. Take for example the python package index; the ability to mirror and host your own pypi has made the ecosystem more robust and pluggable, to the extent that organizations have built infrastructure on the ability to do so. While private registries discourage sharing code, they increase usability/pluggability, and make the ecosystem more robust in the end.

What about fragmentation concerns you here?