You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 23, 2024. It is now read-only.
When creating a VM Cortex stores the purpose as a comment but also pushes this to ServiceNow's description field for the VM. On Linux VMs the ServiceNow comment is used to create the MOTD.
Currently there is nothing that updates ServiceNow if someone changes the comment in Cortex. (And thus MOTD doesn't update).
This has lead to a lot of VMs where the comment in Cortex is out of sync with ServiceNow.
I suggest we may want an API call to change the ServiceNow comment when updating in Cortex - or a task that routinely syncs them etc.
The text was updated successfully, but these errors were encountered:
I've edited the edit (Settings) and view page to display a read only copy of the CMDB comment / desc so it is clear what each is set to. Currently it might be a bad idea to sync these back up to Service Now as there are a fair few mismatches.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When creating a VM Cortex stores the purpose as a comment but also pushes this to ServiceNow's description field for the VM. On Linux VMs the ServiceNow comment is used to create the MOTD.
Currently there is nothing that updates ServiceNow if someone changes the comment in Cortex. (And thus MOTD doesn't update).
This has lead to a lot of VMs where the comment in Cortex is out of sync with ServiceNow.
I suggest we may want an API call to change the ServiceNow comment when updating in Cortex - or a task that routinely syncs them etc.
The text was updated successfully, but these errors were encountered: