Hi Dimutu, How about using a metadata service for this. Metadata service is a REST service where its provides APIs to publish and fetch key value/values pairs. This is already implemented in Stratos.
So workflow is, Instead of writing to git, AF publishes to metadata service. Then cartridge agent fetches from the metadata service and expose as env variable. I feel this is more cleaner than commiting to repo. Touched, not typed. Erroneous words are a feature, not a typo. On Nov 8, 2014 10:33 PM, "Dimuthu Leelarathne" <dimut...@wso2.com> wrote: > > Hi all, > > For propagating resources (name-value pairs for Apps) to none-carbon > runtimes we need an approach. I have been thinking about the possibilities > and this came into my mind. > > https://creately.com/diagram/i296mkhn1/kguXC7mpUdJsUELKTcjbNrrT4%3D > > WDYT? Are there different suggestions? Or improvements? > > thanks, > dimuthu > > -- > Dimuthu Leelarathne > Architect & Product Lead of App Factory > > WSO2, Inc. (http://wso2.com) > email: dimut...@wso2.com > Mobile : 0773661935 > > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
