Since Terraform is an external piece of software that would be used to provision base infrastructure and then leverage Davids provider for wskdeploy, MPL license doesn't matter since its packaged and distributed and downloaded separately.
As far as your provider, if you are building the provider together with wskdeploy and distributing together as single unit make your provider license apache2 friendly and should be fine On Fri, Jul 7, 2017 at 6:20 AM, David ZL Liu <[email protected]> wrote: > Thanks for your encouragement Dragos. I'm a terraform newbie, one possible > benefits I can think of is maybe > we could use one configuration to deploy openwhisk packages more > conveniently with minimum changes, we could also > introduce current wskdeploy yaml as a complement. > > Terraform is currently supported by many mainstream cloud providers such > as AWS, google etc. Through the github repo > we could say they update frequently. > https://github.com/terraform-providers. > > But one possible issue needs to consider is Terraform used MPL2.0 license. > > Cheers, > dliu > > > > > > > From: Dascalita Dragos <[email protected]> > To: [email protected], [email protected] > Date: 2017-07-07 上午 10:49 > Subject: Re: terraform wskdeploy plugin demo > > > > Nice work David ! Would you be able to highlight the advantages you > observed from using terraform with wskdeploy ? Were you able to also > factor in terraform's state ? > > Thanks, > Dragos > > On Thu, Jul 6, 2017 at 10:34 PM David ZL Liu <[email protected]> wrote: > > > Greetings, > > > > I made a simple demo app for wskdeploy as a terraform plugin, so is > there > > any one interested > > in integrate wskdeploy or other OpenWhisk related tools to terraform? > You > > could reference the code > > here:https://github.com/lzbj/TerraformPlugin_Demo, thanks. > > > > > > Cheers, > > dliu > > > > > > > > > > >
