Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-19797

Template-resolver should output current resource state

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • ACM 2.15.0
    • None
    • GRC
    • None
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Provide the required acceptance criteria using this template.

      • ...
      Show
      Provide the required acceptance criteria using this template. ...
    • GRC Sprint 2025-08, GRC Sprint 2025-09, GRC Sprint 2025-18, GRC Sprint 2025-20, GRC Sprint 2025-19
    • None

      Value Statement

      In https://issues.redhat.com/browse/ACM-17214, we added the ability for template-resolver to output YAML of all of the resources that the template uses, for example via a `lookup` call. However, the tool does not return the current state of the object(s) that the policy would manage. This information would be helpful for a full end-to-end understanding of what the policy will do if it was applied, in coordination with the dryrun tool.

      From feedback posted in https://issues.redhat.com/browse/ACM-14937 

      Definition of Done for Engineering Story Owner (Checklist)

      • The template-resolver should be able to output YAML of the current state of the resources defined by the policy. For example, a policy managing a ConfigMap should output the current state of that ConfigMap. 

      Development Complete

      • The code is complete.
      • Functionality is working.
      • Any required downstream Docker file changes are made.

      Tests Automated

      • [ ] Unit/function tests have been automated and incorporated into the
        build.
      • [ ] 100% automated unit/function test coverage for new or changed APIs.

      Secure Design

      • [ ] Security has been assessed and incorporated into your threat model.

      Multidisciplinary Teams Readiness

      • [ ] Create an informative documentation issue using the Customer

      Portal Doc template that you can access from [The Playbook](

      https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

      and ensure doc acceptance criteria is met.

      • Call out this sentence as it's own action:
      • [ ] Link the development issue to the doc issue.

      Support Readiness

      • [ ] The must-gather script has been updated.

              jalaw@redhat.com Janelle Law
              jkulikau@redhat.com Justin Kulikauskas
              Derek Ho Derek Ho
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: