Python code that is used in customer scripts should pass pep8 and flake8 linting

See relevant ticket #44206

Specifically, David needs to add function to certain stage of customized Setup workflow, e.g. add_to_configuration(function, components). Current Workflow class enforces this function to have two parameters. This is enforced by _validate_function(self, func) of the Workflow class. Normal use of this function is to pass in sandbox (1st parameter) and sandbox's certain components (2nd parameter).

However, in his implementation, David wants to use a class function (to add to Setup work flow), and the class already has sandbox data member, and his script can't pass lint. Basically, David points out current restriction by the current Workflow class is too rigid and should be relaxed.

Hi Song,

I understand that the OOTB scripts are too strict for your need.

Can you please explain why the option to use custom script or copy the OOTB script and change it will not answer the need?

Hi Gilat,

Changing the script is the solution. I added some details on this in the ticket 44206

Still it's a valid request to merge these changes into the OOTB library as well.

OK, thanks Natti! Can't wait to see the votes on this idea.

The alternative is to implement a separate workflow class that can enforce different structure as a baseline for orchestration scripts. The workflow can be published as a separate Python package for other users' use.