Change Request Types Accepted by Ansible Collection for SNOW
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello,
We're trying to use the Ansible Collection for SNOW; however, it appears that the change request role only allows "Emergency, Normal or Standard".
Our SNOW team requires us to use something I believe to be custom, "Technology Change".
Our use-case is intended to provide a fully automated mechanism to make some changes on devices after the change has been approved.
The flow is:
1. User Submits the parameters they want.
2. If it validates we submit a change request (this works)
3. An approver reviews the change and schedules it
4. When it is in the "Scheduled" state, Red Hat Event Driven Ansible (EDA) will pick it up
5. EDA will call a workflow template to implement the change...
If we pass, "normal" the flow works as described. If we pass "Technology Change" the change gets submitted, but it's in a state where we can't do anything with it.
We're using the same CI in both cases (Normal and Technology Change), but the process just doesn't seem to put the change into a condition where it can be approved and scheduled. When I look at the payload, it seems that type is null. Additionally, when I look at what I believe to be the code (https://github.com/ansible-collections/servicenow.itsm/blob/main/plugins/modules/change_request.py), it seems to reenforce that we can only pass one of the 3 types listed.
If we're understanding this correctly, what reasons might there be against allowing custom types. I'd imagine that we can submit a request to allow custom types, but I'm not sure if that makes sense so wanted to get the take of someone who might be more familiar.
Thank you
