You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The skeleton is a great idea to help standardize module development. The Puppet development tools are experiencing rapid progression and while the skeleton helps with the creation of a new module, the question I have pondered is how it can be applied to update an existing module? The rspec-puppet and beaker tools are tightly integrated with the module and thus complicate the update of the "framework" elements. One possible method involves using the latest version of the skeleton to generate a project where the manifests, unit tests, and acceptance tests are removed and stored within a VCS. The capabilities of the VCS are then used to merge the framework elements with the existing project. Has anyone else considered the evolution of the framework elements for a module?
The text was updated successfully, but these errors were encountered:
You can do some of this with modulesync. I've been meaning to look at ways of providing a way of using the two together but never quite had time.
It's definitely a worthwhile endeavour. My guess is it will require higher level tools, ie. either extending or replacing the existing Puppet Module Tool. I'd had this as a topic to talk to some folks about at the Community Summit at PuppetConf if you're going to be around.
The skeleton is a great idea to help standardize module development. The Puppet development tools are experiencing rapid progression and while the skeleton helps with the creation of a new module, the question I have pondered is how it can be applied to update an existing module? The rspec-puppet and beaker tools are tightly integrated with the module and thus complicate the update of the "framework" elements. One possible method involves using the latest version of the skeleton to generate a project where the manifests, unit tests, and acceptance tests are removed and stored within a VCS. The capabilities of the VCS are then used to merge the framework elements with the existing project. Has anyone else considered the evolution of the framework elements for a module?
The text was updated successfully, but these errors were encountered: