Closed kridSeppi closed 4 months ago
the ome_configuration_compliance_baseline module could be extended.
when remediating a configuration baseline, the job is executed immediately. this creates problems when a reboot is included.
In OME it is possible to
maybe:
- name: Remediate specific non-compliant devices to a configuration compliance baseline using device service tags dellemc.openmanage.ome_configuration_compliance_baseline: hostname: "192.168.0.1" username: "username" password: "password" ca_path: "/path/to/ca_cert.pem" command: "remediate" names: "baseline1" device_service_tags: - "SVCTAG1" - "SVCTAG2" schedule: stage schedule_intervall: next_reboot - name: Remediate specific non-compliant devices to a configuration compliance baseline using device service tags dellemc.openmanage.ome_configuration_compliance_baseline: hostname: "192.168.0.1" username: "username" password: "password" ca_path: "/path/to/ca_cert.pem" command: "remediate" names: "baseline1" device_service_tags: - "SVCTAG1" - "SVCTAG2" schedule: stage schedule_intervall: once scheduleStart: "2024-03-01T10:00:00.000Z"
@kridSeppi , thank you for submitting this feature request. This is added to the backlog and will be prioritized accordingly to be delivered over the future releases.
the ome_configuration_compliance_baseline module could be extended.
when remediating a configuration baseline, the job is executed immediately. this creates problems when a reboot is included.
In OME it is possible to
maybe: