CPILint 1.0.3 brings new ways to inspect your iflows
Yesterday, I released version 1.0.3 of CPILint (you can download it here). If this is the first time you hear about CPILint, let me very briefly introduce the tool to you. CPILint is an open source, command-line tool for SAP Cloud Integration that lets you automate the governance of your integration flows. You do so by choosing rules that you want your iflows to adhere to. The tool then does the heavy lifting of checking your iflows for compliance. CPILint ships with rules covering best practices, security, scripting, connectivity and more. For a much more in-depth introduction to CPILint, please see this previous blog post of mine.
The new version brings a bunch of rules up to date with the new adapter types that have been introduced since CPILint was originally released. But more importantly, it introduces new and rather useful ways to specify which iflows you want to inspect in your CPI tenant.
Prior to version 1.0.3, you had two options: You could either inspect every iflow in the tenant (optionally skipping SAP packages) or any number of individual iflows.
With the new
-packages command-line option in 1.0.3, you can now choose to inspect only the iflows in specific packages. If you want to inspect all iflows in the tenant except for certain packages, you can use the new
-skip-packages option to skip those packages.
If you keep your iflows in the draft state while working on them, you might want to hold off on inspecting them until they are finished and saved with a version number. The new
-skip-drafts command-line option lets you do just that.
In summary, the new command-line options enable you to be a lot more precise about exactly which iflows you want CPILint to inspect. In turn, you won’t have to bother with compliance issues that are not relevant.
To keep the names of the command-line options consistent, the existing
-retrieve-ids option has been renamed
-iflows (it was a pretty bad name to begin with – sorry about that!). The
-skip-ids option has been renamed
-skip-iflows. If you call CPILint from an existing script, please make sure to update the option names when upgrading to version 1.0.3.
Oh, and the CPILint wiki has a new page listing the changes, fixes and new features introduced with each new version of CPILint.
Have fun playing around with the new version! As always, do let me know if you run into issues or if you have suggestions for improvements or new features.
Hi Morten, I've just added a GitHub issue with a feature request to implement a Groovy coding best practice check. Just an idea and think it could be helpful. 🙂
It's an intriguing idea 🙂 It would have to use an existing static analysis library, and since best practices mean different things to different people, it would have to be highly configurable. Ideally with an XML configuration option, so that it could be embedded directly in the rules file.
I'll look into it some more.