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
I'm working on customizing a skeleton for our own internal use. The metadata has a default License value of Apache-2.0 in the puppet codebase The skeleton comes with a LICENSE file that is the Apache 2.0 License.
When we create our internal modules, they are all under our own custom license. We obviously can put our own license in the templated LICENSE file, but is there any way to set the 'default' value of the interview questions in the skeleton, or via config somewhere?
One solution is to modify the metadata.json.erb to supply our license, but then you lose any ability for the interview question to be supplied with an alternative answer. Since there is a default license value, I can't just check on nil. I could do some sort of ENV var magic inside of the metadata.json.erb.
Any thoughts or suggestions? Should I open up a ticket about adding configurable default parameters for puppet module generate on the puppet JIRA tracker? If there was some way to put default options in your skeleton in the module_skeleton_dir that puppet module generate would check, that would be a pretty clean implementation.
The text was updated successfully, but these errors were encountered:
I'm working on customizing a skeleton for our own internal use. The metadata has a default License value of Apache-2.0 in the puppet codebase The skeleton comes with a LICENSE file that is the Apache 2.0 License.
When we create our internal modules, they are all under our own custom license. We obviously can put our own license in the templated LICENSE file, but is there any way to set the 'default' value of the interview questions in the skeleton, or via config somewhere?
One solution is to modify the metadata.json.erb to supply our license, but then you lose any ability for the interview question to be supplied with an alternative answer. Since there is a default license value, I can't just check on nil. I could do some sort of ENV var magic inside of the metadata.json.erb.
Any thoughts or suggestions? Should I open up a ticket about adding configurable default parameters for puppet module generate on the puppet JIRA tracker? If there was some way to put default options in your skeleton in the module_skeleton_dir that puppet module generate would check, that would be a pretty clean implementation.
The text was updated successfully, but these errors were encountered: