-
Notifications
You must be signed in to change notification settings - Fork 3
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
Why 3 modules? OSS vs. PRO vs. HA #1
Comments
And a possible follow-up, depending on your answer: If you'd consider to merge all three modules into one module, I'd like to help adding support for the PRO version to fervidus/artifactory. |
ping @bryanjbelanger |
HI Frank,
I was trying to be creative.
Pro builds on HA. HA builds upon both.
It did remove lots of redundant stuff. In retrospect it could of been done in one module.
I need to look at this and get it hooked up to Travis CI.
Thanks for looking into this,
Bryan Belanger | Principal Consultant
phone: +1 (248) 613-2538 | email: [email protected] <mailto:[email protected]>
… On Oct 15, 2019, at 12:07 PM, Frank Wall ***@***.***> wrote:
ping @bryanjbelanger <https://github.com/bryanjbelanger>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=ACBKLJC3FLTSCZVZFPWTLNDQOXTCVA5CNFSM4I4VCSEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBJKSWQ#issuecomment-542288218>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACBKLJFSYCTFSEJIFGH7H2LQOXTCVANCNFSM4I4VCSEA>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi guys,
since the README does not mention any reasons... I was wondering why you've decided to split the Artifactory management into three different modules. For example, the module for the OSS version seems to be much more capable with regards to configuration options. So, at least for me, there's no easy way to switch (from the OSS) to the PRO module without changing everything.
My usual approach would be to support all three editions with just one module. This would make the Puppet code more complicated, but in the end it would probably save time on module maintenance. So I'd assume that there must be pretty serious reasons to create three different modules.
Thanks
Frank
The text was updated successfully, but these errors were encountered: