Third party heat resouce plugin for Amazon Cloud Formation

asked 2014-11-19 05:34:54 -0500

Pradip gravatar image


It is understood that one can extend the Resource types for third party services.

Now if one wants to extent the resources and used the AWS CloudFormation template, how different it would be than just extending for the native OpenStack resources.

So in a nutshell, the purpose here is to define some of the third party resources inside Heat and write the template only in terms of CloudFormation.

Any such document would be helpful.

Thanks, Pradip

edit retag flag offensive close merge delete


I'm not quite sure what you're asking. You want to write Heat plugins to drive AWS instead of OpenStack? Or you want to write templates that can still be launched by CloudFormation even though they contain custom resource types? Or you want to use custom resource types with the CFN template format?

zaneb gravatar imagezaneb ( 2014-12-08 11:11:33 -0500 )edit

Ok. I think (later on) I understand it. So heat plugins can be written of in JSON format also. So as far as Amazon plugin format is concerned, there is nothing special as such. It is simple JSON format and heat-eng processes that. So for a plugin provider, it is immaterial whether json/yml. Right?

Pradip gravatar imagePradip ( 2014-12-08 21:38:34 -0500 )edit

We usually use the term 'plugin' to refer only to Python plugins.

But yes, wherever Heat accepts a template (including for template resources, aka provider resources) it can be in any of the formats that Heat supports.

zaneb gravatar imagezaneb ( 2014-12-09 07:53:01 -0500 )edit