Adding Support to Suppress Validators in Custom Resources

[himani2411]

Description of changes

• Adding Support to suppress validators in Custom Resources

Tests

• Integ Test

{%- import 'common.jinja2' as common with context -%}
---
test-suites:
 custom_resource:
   test_cluster_custom_resource.py::test_cluster_create:
     dimensions:
       - oss: ["alinux2"]
         regions: ["us-east-1"]
         instances: {{ common.INSTANCES_DEFAULT_X86 }}
   test_cluster_custom_resource.py::test_cluster_create_invalid:
     dimensions:
       - oss: ["alinux2"]
         regions: ["us-east-1"]
         instances: {{ common.INSTANCES_DEFAULT_X86 }}
   test_cluster_custom_resource.py::test_cluster_update:
     dimensions:
       - oss: ["rocky8"]
         regions: ["us-east-1"]
         instances: {{ common.INSTANCES_DEFAULT_X86 }}
   test_cluster_custom_resource.py::test_cluster_update_invalid:
     dimensions:
       - oss: ["alinux2"]
         regions: ["us-east-1"]
         instances: {{ common.INSTANCES_DEFAULT_X86 }}
   test_cluster_custom_resource.py::test_cluster_update_tag_propagation:
     dimensions:
       - oss: [ "ubuntu2004" ]
         regions: ["us-east-1"]
         instances: {{ common.INSTANCES_DEFAULT_X86 }}
   test_cluster_custom_resource.py::test_cluster_delete_out_of_band:
     dimensions:
       - oss: ["ubuntu2204"]
         regions: ["us-east-1"]
         instances: {{ common.INSTANCES_DEFAULT_X86 }}
   test_cluster_custom_resource.py::test_cluster_delete_retain:
     dimensions:
       - oss: ["rocky9"]
         regions: ["us-east-1"]
         instances: {{ common.INSTANCES_DEFAULT_X86 }}
   test_cluster_custom_resource.py::test_cluster_create_with_custom_policies:
     dimensions:
       - oss: ["rhel8"]
         regions: ["us-east-1"]
         instances: {{ common.INSTANCES_DEFAULT_X86 }}

References

• Link to impacted open issues.
• Link to related PRs in other packages (i.e. cookbook, node).
• Link to documentation useful to understand the changes.

Checklist

• Make sure you are pointing to the right branch.
• If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
• Check all commits' messages are clear, describing what and why vs how.
• Make sure to have added unit tests or integration tests to cover the new/modified code.
• Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[codecov]

Codecov Report

Attention: Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.

Project coverage is 90.22%. Comparing base (443e33d) to head (15ebef7).
Report is 16 commits behind head on develop.

❗ Current head 15ebef7 differs from pull request most recent head c6e4511

Please upload reports for the commit c6e4511 to get more accurate results.

Files	Patch %	Lines
cli/src/pcluster/lib/lib.py	66.66%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #6253      +/-   ##
===========================================
- Coverage    90.23%   90.22%   -0.01%     
===========================================
  Files          181      181              
  Lines        15874    15875       +1     
===========================================
  Hits         14324    14324              
- Misses        1550     1551       +1     

Flag	Coverage Δ
unittests	90.22% <66.66%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.