IMO this will create maintainability issue. We need to maintain all the separate hieradata structure for each scenarios.For the one particular alternation we need to change whole set of files.
Why can't we do this by using defined types in Hiera and lookup parameters for a given instance? Based on the identify keys we set for each vm, docker, K8S etc we can select the appropriate data set from Hiera file. Thanks, Gayan On Sat, Apr 9, 2016 at 8:28 AM, Imesh Gunaratne <im...@wso2.com> wrote: > > On Fri, Apr 8, 2016 at 7:48 PM, Isuru Haththotuwa <isu...@wso2.com> wrote: >> >> >> hieradata >> |--- dev >> |--- wso2 >> |---- <product_name> >> |--- <product_version> >> |-- *vm* >> |-- >> default.yaml >> |-- >> manager.yaml >> |-- >> worker.yaml >> |--* docker* >> |-- >> default.yaml >> |-- >> manager.yaml >> |-- >> worker.yaml >> |-- *kubernetes* >> >> |-- >> default.yaml >> |-- >> manager.yaml >> |-- >> worker.yaml >> >> > +1 for the suggestion Isuru, will proceed with this. We can add other > platforms such as OpenShift, Mesos, Cloud Foundry on the same level. > > Thanks > >> >> >> Thanks >>> >>> -- >>> *Imesh Gunaratne* >>> Senior Technical Lead >>> WSO2 Inc: http://wso2.com >>> T: +94 11 214 5345 M: +94 77 374 2057 >>> W: http://imesh.io >>> Lean . Enterprise . Middleware >>> >>> >> >> >> -- >> Thanks and Regards, >> >> Isuru H. >> +94 716 358 048* <http://wso2.com/>* >> >> >> > > > -- > *Imesh Gunaratne* > Senior Technical Lead > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: http://imesh.io > Lean . Enterprise . Middleware > > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Gayan Gunarathne Technical Lead, WSO2 Inc. (http://wso2.com) Committer & PMC Member, Apache Stratos email : gay...@wso2.com | mobile : +94 775030545 <%2B94%20766819985>
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
