Make it less linked to Puppet / PDK

[ahmet2mir]

This is probably one of the best templating system I used but it's too linked to puppet.
This tool is just awesome and could bery useful for much more people than puppet communty :)

Commands like "new, convert, update" are not linked to pdk, but other "test, build release" etc are.

Is it possible to make them configurable from pct-config.yml ? so each "project" type will have their own test/build/release commands ?

For example if I have a makefile in the template I could define it as

---
template:
  id: example-project2
  type: project
  display: Example Project
  version: 0.1.0
  url: https://github.com/somewhere

example_project2:
  build: make build
  test: make test
  release: make release
  variables:
    lorem: ipsum

You just "createCommand" from pct and exec it without relying on pdk.

[sanfrancrisko]

Thanks @ahmet2mir for the positive feedback!

We're going to announce a new strategy for the PCT product very soon, but to summarise, we're moving to a smaller, more decoupled from PDK approach. So the idea will be that this is a lot more standalone from PDK.

More details soon.

[sanfrancrisko]

Ultimately, this is a Puppet product and the primary use case will be geared towards the Puppet ecosystem. Check out the team's strategy for PCT here: https://puppet.com/blog/the-future-of-the-puppet-developer-kit-pdk/