We are looking to integrate ServiceNow change requests into concourse.
The thought was to create a resource for it but wanted a little feedback as to best practices and how to implement this.
The use case is this…
- in a job we want to create a NEW change request
- the next job in the pipeline wants to get that CR (hopefully from a resource) and update it
- more jobs will also want to use the CR to update it
- in a final job we will close the CR.
The concerns we have is this doesn’t really fit in a resource. There will be no “check”, the “in” is definitely used as is the “out” but check doesn’t really make sense since it would be difficult to write in this sort of scenario and anything we did would seem a little hacky.
Has anybody else implemented a change request flow as a resource (using service now or some other change request system)? How did you do it? How does it work?
We also thought this fits in our env with a “pool” as we use pools to lock the env and so wanted to know if this could integrate with the pool “metadata”.
We usually “lock” the env in our first step (which would then create the CR) at this point we would want to save the CF number as part of the metadata.
Then all the subsequent jobs would read the lock metadata and use that CR info.
Our final step which releases the lock would also clear out the metadata.
Has anybody used this flow or would recommend a way to implement it this way?