feat: add resource rules to krm-kcl spec

[shruti2522]

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

• [ ] N
• [x] Y

fix #13

2. What is the scope of this PR (e.g. component or file name):

kcl-lang/krm-kcl/pkg/options/testdata/resource_list

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

• [x] Affects user behaviors
• [ ] Contains syntax changes
• [ ] Contains variable changes
• [ ] Contains experimental features
• [ ] Performance regression: Consumes more CPU
• [ ] Performance regression: Consumes more Memory
• [ ] Other

Added resource matching rules to the krm-kcl spec

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

• [ ] N
• [x] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

• [ ] Unit test
• [ ] Integration test
• [ ] Benchmark (add benchmark stats below)
• [ ] Manual test (add detailed scripts or steps below)
• [x] Other

[shruti2522]

Please take a look, @Peefy

[Peefy]

I think we should first implement this feature in the corresponding code before modifying the test cases.

[shruti2522]

I have added the MatchConstraints struct and the function to verify resource matching rules to config.go @Peefy

[Peefy]

Could you please fix the CI?

[shruti2522]

I have modified the test cases in config_test.go to address the errors, and make test works fine now.

PASS
ok      kcl-lang.io/krm-kcl     7.814s
shruti@fedora:~/cncf/krm-kcl$

[shruti2522]

I think we should use the resourceRules field directly, and remove matchConstraints to resolve the following errors while testing.

FAIL: TestRunLocalPath (0.00s)
    --- FAIL: TestRunLocalPath/resource_list (0.00s)
        run_test.go:72: TestRunLocalPath() error = yaml: unmarshal errors:
              line 10: cannot unmarshal !!map into []config.ResourceRule, wantErr false

Is this the correct approach @Peefy.

[Peefy]

I suggest keeping this field as it is consistent with Kubernetes CEL, please refer to https://kubernetes.io/docs/reference/access-authn-authz/validating-admission-policy/#creating -A-validatingadmissionpolicy

[shruti2522]

Any ideas on what might be causing this error @Peefy, since I have tried out correcting any possible syntax or test case error.

[shruti2522]

Done with the changes @Peefy