New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[question] more types/providers #373
Comments
I think having types/providers for all foreman resources would be a good addition. I'm not sure what the best way to proceed is. Looking at the current types they are all rather minimal in terms of documentation and sometimes have hardcoded defaults. Another difference is that we use our Apipie bindings (see https://github.com/theforeman/puppet-foreman/blob/master/lib/puppet/provider/foreman_smartproxy/rest_v2.rb) which would also be preferred. Maybe we should first work on one type, see what the exact changes need to be and then repeat it for all other types? |
Ok, sure. I'll raise the first PR this week and we can work from there. I'll keep this issue open to keep track of the PRs. |
Awesome! |
@liamjbennett any luck so far? need help? |
+1 for types for configuring foreman. In particular, I'd be interested in a type to configure foreman |
Is there still interest in this being contributed? I have some dedicated time at work to spend on it and can contribute if there's someone available for reviews / direction. |
@mdwheele I think there is. Personally I'm not that familiar with types and providers but I'll be happy to do some reviews/testing. |
Closing, as we answered the question, but noting that there was no respective PR. |
Hi, We have been using this a fork on this module to puppetize our foreman instance for a while now. Our fork contains a large number of types/providers for configuring foreman itself. Is this something you'd like to see contributed back? If so, would you prefer it was small PRs for each type/provider or a one larger one?
https://github.com/opentable/puppet-foreman/tree/master/lib/puppet/type
The text was updated successfully, but these errors were encountered: