The oc, kubernetes, helm, az, 'gcloud' and terraform plugins make use of:
the native command line tools of the various technology stacks. They deliberately do not want to establish
a new Java-based API and instead focuses on what developer already know and bring it to Gradle. It further helps
to stay up-to-date with those technologies and keep the plugins simple.
dockerizization of the command line tools to gain isolation of their configuration to the scope of the
applied Gradle project and have platform independence and caching of the tools.
Volume-mappings into the project to let different plugins work together, such as sharing the Kubernetes configuration.
generated wrapper scripts in the project root to give access to the tools from the command line
just like if they were locally installed while hiding volume-mapping and environment logic.
Note that early versions of plugins did not yet make use of dockerization. The extensions can still be configured to fallback
to that behavior. This functionality may or may not be removed in the future depending on the need.
请发表评论