Uploaded image for project: 'Ansible Automation Platform RFEs'
  1. Ansible Automation Platform RFEs
  2. AAPRFE-2124

Support for Listing and Deleting/Disabling Schedules in ansible.controller Collection

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      1. What is the nature and description of the request?
        The customer requests expanded functionality within the ansible.controller Ansible collection to support the management of job template schedules. 
        Specifically, they are seeking the ability to:
        • Search or list schedules associated with a given job template (by name or ID)
        • Disable or delete schedules via modules (rather than using ansible.builtin.uri or direct API calls)

      Currently, the collection allows for schedule creation and updates, but lacks built-in capabilities for disabling, deleting, or listing schedules, forcing users to rely on lower-level API interactions.

      1. Why does the customer need this? (List the business requirements here)
        • The customer automates job schedule management based on timezones stored in a ServiceNow Configuration Item (CI).
        • When a timezone no longer has hosts, any remaining schedule linked to it results in "no hosts matched" errors, which are disruptive and misleading.
        • To maintain a clean, accurate scheduling environment, the customer needs to dynamically identify and disable/delete such orphaned schedules.
        • Managing this via direct API calls adds development complexity and increases maintenance overhead.
        • Having native Ansible modules for this purpose would improve automation reliability, reduce custom scripting, and ensure better alignment with AAP-supported tools.
      1. How would you like to achieve this? (List the functional requirements here.)
        • Enhance the existing "ansible.controller.schedule" module to support:
          • Listing/searching schedules based on job template name or ID
          • Disabling a schedule (i.e., setting it inactive without deletion)
          • Deleting a schedule cleanly via the module
        • Optionally include filters (e.g., by enabled status, next run time) to better target schedules for modification
        • Ensure idempotent behavior consistent with Ansible best practices

              rh-ee-rreed Ron Reed
              rhn-support-apaygavh Abhishek Paygavhan
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: