# adding support for proprietary features to modules **URL:** \ **Category:** Ansible Developer\ **Tags:** ee\ **Created:** [September 30, 2013, 3:17pm UTC](https://forum.ansible.com/t/adding-support-for-proprietary-features-to-modules/13580 "2013-09-30T15:17:00Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![James\_Martin2](https://avatars.discourse-cdn.com/v4/letter/j/b9e5f3/32.png) [@James\_Martin2](https://forum.ansible.com/u/James_Martin2)\ **Post date:** [September 30, 2013, 3:17pm UTC](https://forum.ansible.com/t/adding-support-for-proprietary-features-to-modules/13580/1 "2013-09-30T15:17:00Z")
I'm the author of Ansible's Riak module. We have some closed-source features in our enterprise product, Riak EE, that are not currently exposed in the existing Riak module, one being multi-datacenter replication. We'd like to add some code to the module to make these feature available. All the new bits in the module would be open, of course, and it would be documented that Riak EE is required for the features to work. I'm guessing exposing proprietary features is ok since there are a number of modules already that work with proprietary hardware and APIs, but just wanted to confirm. Thanks, James ---
**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\ **Post date:** [September 30, 2013, 3:51pm UTC](https://forum.ansible.com/t/adding-support-for-proprietary-features-to-modules/13580/2 "2013-09-30T15:51:47Z")
Completely ok! -- Michael ---
**Author:** ![James\_Cammarata1](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@James\_Cammarata1](https://forum.ansible.com/u/James_Cammarata1)\ **Post date:** [September 30, 2013, 4:31pm UTC](https://forum.ansible.com/t/adding-support-for-proprietary-features-to-modules/13580/3 "2013-09-30T16:31:13Z")
I agree, I don’t have a problem with this as long as it’s clearly documented as such.