How can I influence which Fabric managed containers may become Fabric Git Master?
Issue
In a Fabric managed environment, every Fabric container maintains its own local copy of the internal git repository that is used to manage the Fabric profile information.Every Fabric managed container may potentially become the git master.
Is there a way to control which containers may become a git master in Fabric? Is there a way to configure Fabric so that only a subset of Fabric containers can ever become a git master?
Environment
- Red Hat Fuse
- 6.3
- 6.2.1
- Fabric mode
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.