{"push_id":2431416438,"size":1,"distinct_size":1,"ref":"refs/heads/shw-update-api-tokens","head":"9fb91c5ed0ac733d441a05a39575c5f28418c665","before":"85ada8b1916321c21cd7231fc03ac9c27c42feeb","commits":[{"sha":"9fb91c5ed0ac733d441a05a39575c5f28418c665","author":{"name":"Samuel Williams","email":"992919eb94dcce41206437f97ea8b3155055bcbe@digital.cabinet-office.gov.uk"},"message":"Add jobs for rotating tokens\n\n ## Summary\nAdds a new pipeline that allows for easily rotating data/search API\ntokens in a given environment. Also updates the existing job for\nreleasing an application to paas to allow building without specifying\na release version. In this case, it will determine the existing release\nby finding the app's primary route (via CF CLI) and hitting its\n`_status` endpoint to find the current release tag. After doing that, it\nwill re-release that same version to PaaS, allowing new configuration to\nbe pulled in. The detection and deployment happens within the specific\napp and stage's Jenkins lock, meaning it is effectively atomic and so\nasynchronicity should not be a concern.\n\n ## Ticket\nhttps://trello.com/c/4crGe6F0/169","distinct":true,"url":"https://api.github.com/repos/alphagov/digitalmarketplace-jenkins/commits/9fb91c5ed0ac733d441a05a39575c5f28418c665"}]}
{"actor":{"display_login":"samuelhwilliams"}}