Remove python module support about sceptre HOT 5 CLOSED

Not sure it would be fair to say no ones using it - I've seen it used a lot in custom hooks. I think we still need to strive for consistency as it make developing a lot easier.

Do you see this just in the scope of documentation and versioning - or any code structure changes you see happening?

Maybe good to look at Hashicorp Vault and see how they manage a CLI and restful API in the same code base. Possibly could do a complete separation with sceptre-core and sceptre-cli? We also need to consider how this restricts future extension to the project e.g. what if someone wants to wrap sceptre with flask etc...

What issues have we run into so far with this supporting both?

from sceptre.

In some customers we are seriously considering using the module. I would MUCH rather prefer you don't remove it without offering another alternative API first.

from sceptre.

Hm okay if we keep it we still need some way of fixing the versioning issue. Separating the CLI from the Python core would do that as @seanrankine mentioned. Sean how do Hashicorp do it?

I guess we could have two repositories, sceptre and sceptre-core. sceptre-core would implement the Python module, and sceptre would depend on sceptre-core and implement the CLI. Each would have their own version numbers. It does add complexity though.

I think we still need the freedom to be able to change the python internals. I imagine we'd go though sceptre-core version number relatively quickly, and we should warn users that using the CLI will likely give more stable results.

from sceptre.

@jamesroutley I agree with @emiliogarcia and think this would be a nice way to do it.

from sceptre.

Decided to look at having two repositories, sceptre and sceptre-core. Continued in #76

from sceptre.