How to implement feature management in WHM/cPanel?

How to implement feature management in WHM/cPanel?
I have developed a plugin for WHM/cPanel and want to provide an ability to manage its features through the Hosting Packages + package extensions in the WHM/cPanel. I'm a bit new to this so I'd appreciate any feedback or suggestions based on general use-case scenario for shared hosters (how they sell features within Service Plans). These are my questions:

++++++++++++++
If You want to buy cheap web hosting then visit http://Listfreetop.pw and select the cheapest hosting. it can be suitable for all your needs.

Top 200 best traffic exchange sites http://Listfreetop.pw/surf

list of top gpt sites
list of top ptc sites
list of top ptp sites
list of top crypto currency Wallets sites
Listfreetop.pw
Listfreetop.pw
Listfreetop.pw

+++++++++++++++
1. If I have two features in the plugin (for example, "Feature 1" and "Feature 2") and each of them may have 3 states ("Mode 1", "Mode 2", "Off"). Shall I create a separate package extensions for "Feature 1" and "Feature 2" or I can put it under a single package extension so hosting provide will configure each Service Plan with both? I'm thinking about the case when hosters may want to sell those features separately in difference Service Plans. For example, "Service Plan 'Starter'" could have "Feature 1" with default value "Mode 2". But "Service Plan 'Business'" could have "Feature 1" with default value "Mode 1" and "Feature 2" with default value "Mode 2".

2. How hosters with 20+ servers configure Packages across their servers? Is there any special software for WHM/cPanel that could automate configuring Service Packages and package extensions (most likely that could be done via WHMCS but AFAIK WHMCS cannot configure WHM Service Packages with package extensions and package extensions separately).

3. Some of WHM/cPanel hosters have package extras (upselling current service plan with some additional services). Just curios if those "package extras" are managed using the same Hosting Package+package extension or somehow separately?

Sorry for newbie questions and thank you for any comments / ideas / suggestions on the topic.

1. You're being a little too vague for me to wrap my head around what you're saying. I wish I could be more helpful. Perhaps somebody else will understand.

2. When it comes to managing packages across a fleet of servers I imagine most providers use something like puppet/chef/ansible to both place the files as well as keep them up to date.

3. It varies - depending on the package and the upgrade/extra. Many providers use WHMCS and WHMCS has fairly good documentation on most of their stuff.

Congrats on developing a cPanel & WHM plugin! First, I recommend taking a look at our documentation and blog post on package extensions if you haven't already done so:

https://documentation.cpanel.net/dis...age+Extensions
https://blog.cpanel.com/improvements...ge-extensions/

This will provide you with a general understanding of how package extensions work. Onto your questions:

1. You can add multiple feature settings to a single extension. For example, let's say your plugin is named "dog". Here's how you'd add three different settings to the package extension for the "dog" plugin:

Code:
# cat /var/cpanel/packages/extensions/dog
dog_tail_length=normal
dog_species=Dalmatian
dog_spots=y
_NAME=Dog Settings
You can then define the defaut settings for the "dog" package extension across multiple packages when you create them through WHM >> Packages >> Add a Package. Here's an image of how this would look in the WHM UI:

https://imgur.com/a/zn0ZD3S

Thus, you can create multiple packages, each having custom settings defined for the individual package extension.

2. Can you clarify a bit what you mean by "Service Package" in this instance?

3. It depends on how the individual provider chooses to implement upgrade options, however natively through cPanel & WHM you could simply create separate packages for each upgrade path and assign that specific package to the account upon the requested upgrade.

Thank you.

I'll add that cPanel support tends to be very good so if you have any questions, you can always reach out to them directly for assistance

Highly appreciated to all of you for the answers.

I don't have questions regarding cPanel API, creating package extensions in general - it's done already. My main question is about common use-case scenario by shared hosting that use WHM/cPanel.

Basically, which of two options is more preferable for hosters: 1) to have package extension with two features settings as part of WHM/cPanel Hosting Package or 2) to have CLI interface for plugin configuration to config it on per-user basis.
If let's say hoster uses WHMCS then which of two options is better (convenient) for him to use in order to create Service Plans with enabled and configured 3rd party plugin?

udomain webmail
lucky 7 make money
robthebank.info
YaBB.pl
bitcoinget.com
virtono.com
tropico 5 make money
with google make money
make money editing
power host forum