Deprecate OS Heat

[gergnz]

I have no idea how many people use this feature but would like to hear from those who do.

If there is no response, I'd be keen to deprecate OS Heat and focus our efforts purely on Cloudformation support.

Thoughts?

[kornypoet]

This would allow us to clean up the repo quite a bit. From personal experience I know Heat only implements a subset of Cloudformation functionality. We are already chasing the elusive compatibility of AWS as it is with our types.yaml file. I'm in favor of removing it. Perhaps making it a separate gem? That could be involved. I would let the discussion stick around for a while before making any changes though.

[johnf]

I'd advocate for deprecating as well, mainly because of my work on #49. If we do want to go ahead with that approach then the OS Heat code will be totally different or we'd need to convert it into the eclipse style for import.

[pvdvreede]

I only use cfndsl for Cloudformation, so would also be in favour of removing Heat so that we can focus efforts and make cfndsl do the one thing really well.

[kidbrax]

What is OS Heat?

[kornypoet]

https://wiki.openstack.org/wiki/Heat

[kidbrax]

Ah, thanks. I would vote for deprecating and focusing on CF

[et304383]

My two cents: don't try to be Terraform. It tries to be cloud agnostic and sufferers from feature lag as a result.

[stevenjack]

Certainly agree that the OS Heat support whilst potentially useful to a small subset of the cfndsl users overcomplicates and makes improving the current codebase harder than it should be..

[johnf]

I would be for deprecating as well. If Amazon end up providing a schema and I continue my work in https://github.com/johnf/cfndsl/tree/new_types then keeping OS Heat would effectively mean maintaing two totally separate code bases.

[kornypoet]

Moving to #257

[gergnz]

This has been removed in 1.0.0.pre branch - be68484
Closing