Page 1 of 1
Unit-type packaging: myth or reality?
Published: July 6, 2018 - 2:11 PM
by louisinger
Hello,
I'm currently thinking about creating my machine groups. Naturally, when I learned about Unit-type packages and what they offer, I immediately started searching everywhere for information on how they worked.
But I can't find anything... neither in the documentation nor on the internet... nothing at all.
My question is therefore quite simple: do Unit packages exist in the Community Edition? If so, how can I create them?
Louis
Re: Unit-type package: myth or reality?
Published: July 6, 2018 - 6:24 PM
by sfonteneau
That's right!
However, since this is primarily a feature of the Enterprise Edition,
absolutely nothing is done to make creating a Unit package easier in the Community Edition...
In the Enterprise Edition, however, creating Unit packages is seamless through the
Simon
Re: Unit-type package: myth or reality?
Published: July 9, 2018 - 8:15 AM
by louisinger
Is it therefore possible to create Unit packages in the community version?
Re: Unit-type package: myth or reality?
Published: July 9, 2018 - 10:35 AM
by sfonteneau
Yes.
EDIT:
Yes, in the sense that the code to manage unit packages is in the WAPT agent code.
However, this remains a feature of the enterprise version and is not planned for use in the community version.
Re: Unit-type package: myth or reality?
Published: July 9, 2018 - 10:49 AM
by louisinger
Could you give me an overview of this? Or do you have any additional documentation on the subject?
Thank you in advance.
Re: Unit-type package: myth or reality?
Published: July 11, 2018 - 09:18
by louisinger
I don't understand the point of including a feature in the community version if they're going to do nothing to make it easier to use. They might as well put it in the enterprise version right away. WAPT is a superb tool, but this mentality benefits no one...
I'll manage with Unit packages, thanks!
Re: Unit-type package: myth or reality?
Published: July 11, 2018 - 09:45
by htouvet
The concept of a package associated with an organizational unit is not integrated into the community version.
We chose to have the core of the WAPT agent (and especially the security functions) as common as possible between the two versions because it's less expensive to develop and test (the so-called "community" version requires people's time that needs to be paid... just as you may have been paid for your work).
If you create a unit package manually and it works for you, that's great; that's the spirit of open source.
But creating documentation for that takes time.
In terms of "mindset," I think we're quite respectful of our "community," as evidenced by the answers we provide regarding the operation of the "community" version and the relatively detailed documentation.
Re: Unit-type package: myth or reality?
Published: July 11, 2018 - 10:38 AM
by cfargues
Hello,
Following Hubert's response, I am closing this thread. If you require any support with your request, please do not hesitate to contact us directly by phone at 02.40.97.57.55.
Have a good day.