Extend file module functions (for smoother GitOps)

[dennybaa]

Hello there!

KCL being a very capable versatile language should have more file system control functions:

• mkdir
• delete
  And maybe even more than this.

It's essential to have control over transitional file creation/deletion and placement. For instance in my case, I do generate prometheus rules from parameterized KCL definitions as the first step:

cd appsops/rules/graph && mkdir -p rules manifests && kcl -dY ./kcl.yaml
generate_rules:
- graph/rules/common-certmanager.yaml
- graph/rules/common-elasticsearch.yaml
- graph/rules/common-istio.yaml
- graph/rules/common-k8s-events.yaml
- graph/rules/common-k8s-nodes.yaml
- graph/rules/common-k8s-resources.yaml
- graph/rules/common-vector.yaml

This is the configuration entry for the next stage, which proceeds with VMRule manifests generation. Simply there should be enough control in place on where to place the files, how to create or delete them to enable smooth GitOps experience out of box. In fact KCL can be and should be used independently to provide a solid GitOps experience.

[Peefy]

I agree. The file system module have beed added in KCL v0.8 and it needs to be extended more at future.

[shruti2522]

Sounds interesting. Would try to raise a PR covering the mkdir and delete functions.

[Peefy]

Thank you @shruti2522.