Forum Discussion
Post ProdigyHow creating a Python custom library
Hi pmscorca,
That is correct. Here is an example of a custom workload with the extensibility toolkit: https://community.fabric.microsoft.com/t5/Extensibility-Toolkit-Gallery/Fabric-Job-Registry/m-p/5006346
Super UserHi pmscorca,
As has been stated on multiple of your posts now, if you want to protect custom logic, the best way to do that is to create a custom workload in Fabric.
Anything else, even a custom python library, will expose your code to those who care to look for it.
pmscorcaHi, I need to find the right solution and so I'm searching the right answers.
The dev toolkit don't seem mature yet. Providing a workloard means that a customer must already have Fabric, but a product could be purchased before Fabric.
So far I seem to have been getting answers from official documentation rather than from experiences.
Thanks
- apturlov
pmscorca My answer below is from an experience. But as I stated already, you are mixing different goals in a single question. My advise is to separate your goals into different questions and seek the answer for the Python protection code question outside Fabric community as it is irrelevant. There are literally no obstacles in running any custom Python code in Fabric provided it's compatible with the execution environment. Every way of protecting your Python code from abuse and reverse engineering is bound to affect how your code works and it's a matter of experimentation and finding the right balance. Start from making sure that your code runs in Fabric as intended in your private Fabric environment then move towards protection options. In my experience-based opinion Fabric is not going to help you with protection.
