developer-friendly approach.<\/a> It hopes this will let teams visualise the usage of tech quickly and identify drift alongside any other issues that may occur.<\/p>\nIt also aims to set policies that address issues as well as tracking and monitoring progress towards policy goals.<\/p>\n
Main characters of the product<\/h4>\n
A core element of the drift management feature is an open source project that analyses repositories for drift. Another component is that the drift report aspect provides a visual representation of what\u2019s happening within the codebase of an organisation. Complexities are then internalised, and vulnerabilities dealt with quickly.<\/p>\n
Lastly, the policy manager captures and tracks changes and variations in code.<\/p>\n
Why the product is needed<\/h4>\n
Talking to DevOps Online about why the company wanted to design the new feature. Johnson spoke of how the firm noticed the gaps in tooling and wanted to make a difference to this.<\/p>\n
Johnson says: \u201c[Before], organisations had a very small number of very large applications. These days they have a very large number of relatively small applications\u2026. Today there is a gap in tooling. We are now building a platform to comprehend these projects, help to get them towards best practice and to make them more consistent.\u201d<\/p>\n
He continued that the feature \u201cgives you the ability to react to important changes in your code and configuration.\u201d<\/p>\n
Customer focused<\/h4>\n
Ryan Day, Co-Founder and COO at Atomist also spoke to DevOps Online about the building of the new product. He says, \u201cThis announcement around drift management, a lot of it was driven by our customers and there is a need specifically around driving consistency that we are putting at the top of our platform. \u201c<\/p>\n
Day added more about the reasoning behind making the tool. He continues: \u201cIt\u2019s really geared at the idea that this isn\u2019t about dependencies. What if you harvested ports exposed in an application and that manifests inside of a DR file? What if there are secrets inside of Kubernetes configuration that shouldn\u2019t be there? We are effectively an engine to spot, recognise and remediate these kinds of patterns. In a world where everything is code, it sort of sits as a repository. It sits at a ground zero where people can take action.\u201d<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Cloud native company, Atomist, has announced its new Drift Management feature. This will be a component of its software delivery automation platform that provides users with a code consistency engine and visual reporting. Its hoped that the feature, which is now in beta, will bring enterprise and DevOps teams the information they need to ship…<\/p>\n","protected":false},"author":45,"featured_media":20920,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"content-type":"","pmpro_default_level":"","footnotes":""},"categories":[3352],"tags":[3439,70,1931,3437,3438],"yoast_head":"\n
Atomist release drift management feature for cloud native software - DevOps Online North America<\/title>\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n\n\n\n\n\n\t\n\t\n\t\n