I recall someone did look at bluecat in the past but getting access to the actual API proved hard as a non-customer. That means we can help you with the smart proxy part, but not with the bluecat part. If the plugin would be open source, it’s much easier for us to help you though
I assume you developed a standalone plugin? Can you point us to the repo?
Ideally we would transfer it to the foreman github namespace. @Gwmngilfen should be able to help with this.
Getting a repo transferred is indeed possible, and is the preferred method, as it ensures the support of the plugin into the future. We do, of course, give admin rights on the transferred repo back to the author
Let us know if that’s what you’d like to do! Thanks!
i am not an experienced developer and this is also my first ruby project.
as i mentiond the plugin is fully functional, but i think there are a lot of things that could be done better.
ive used the basic structure form the device42 plugin. cause i didnt needed them, i didnt update the integration tests. they will propably need a rework
I can add you to the org so that you can transfer, yes. I’ll do that now. Let me know when done so I can clean up
If there’s an associated Rubygem, then it’d be great if you could add theforeman.rubygems@gmail.com as an author, so that we can push releases to the same gem in the event that you decide to move on
You drop password and token in multiple places in proxy log, it’s considered a security vulnerability. Even usernames should not be logged, but that’s probably not that serious if they are in the DEBUG level which must be explicitly enabled by users.
Enable Travis CI for Rubocop and/or more unit/functional tests
Thanks for your contribution, that is appreciated. Be prepared to co-maintain the project tho, our community can help with occasional bugfixes, packaging and shipping it in the main repository but you still will be the one who understands the codebase the most
Thanks! I’ve created a Bluecat team and added you as an admin, so you can easily add more collaborators as needed. Next steps are fixing up @lzap’s points and then speaking to our @packaging team to get it into the repos
If you want to try to prepare packages here is our repo:
Switch over to rpm/develop and read the README, find infoblox dhcp plugin and copy*paste it. Trial and error should do it, just file PR and our jenkins will perform test builds for you. I can assist you if you are stuck.
Please don’t copy paste it. We have scripts to generate it fresh: ./add_gem_package.sh smart_proxy_plugin smart_proxy_dhcp_bluecat foreman-plugins-nightly-nonscl-rhel7