For the last module we will teardown the Application Service we’ve been working with today. Destruction of Application Services is an easy to complete step that is often overlooked because of the perceived complexity it takes to reverse engineer a new build. Utilizing Postman and f5-newman-wrapper, this is actually a very easy step, and will be incredibly valuable to teams seeking to strive for better Application Lifecycle Management. Because Postman and Newman operate in sequential order, simply reversing the order of creation will result in the correct teardown order. Also, since we’re using the native F5 REST endpoints, all you need is a Resource with a DELETE method.
Return to the Jenkins Dashboard and select New Item
Follow steps 2 & 3 of the last module creating the final Jenkins job
Pipeline Job Name: module_4_jenkinsfile_5
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 | node {
stage('Testing') {
//Run the tests
//sh "python –m /home/snops/f5-automation-labs/jenkins/f5-newman-build/f5-newman-build-5"
}
stage('Removal-Notification') {
//Run SNOPS Container Newman Package Delete Service
//chatops slack message that run has completed
slackSend(
channel: '#jenkins_builds',
color: 'bad',
message: 'Super-NetOps Engineer is about to remove an F5 Service!',
teamDomain: 'f5agilitydevops',
token: 'vLMQmBq2tiyiCcZoNlbmAi0Z'
)
}
stage('Approval') {
//Gate the process and require approval
input 'Delete?'
}
stage('Service-Delete') {
//Run SNOPS Container Newman Package add Node to Pool
sh "f5-newman-wrapper /home/snops/f5-automation-labs/jenkins/f5-newman-build/f5-newman-build-5"
//chatops slack message that run has completed
slackSend(
channel: '#jenkins_builds',
color: 'good',
message: 'Super-NetOps Engineer removed an F5 Service successfully!',
teamDomain: 'f5agilitydevops',
token: 'vLMQmBq2tiyiCcZoNlbmAi0Z'
)
}
}
|
Verify the on the BIG-IP the service has been Deleted