1d:I[2890,["266","static/chunks/870fdd6f-4fcc92c129a57d11.js","970","static/chunks/970-91a3a37cc668faba.js","857","static/chunks/857-3b2a1421afa266d2.js","965","static/chunks/app/podcasts/episode/%5BpodcastEpisodeGuid%5D/page-e939c6b91b4a25d4.js"],"default"] 1e:I[1318,["266","static/chunks/870fdd6f-4fcc92c129a57d11.js","970","static/chunks/970-91a3a37cc668faba.js","857","static/chunks/857-3b2a1421afa266d2.js","965","static/chunks/app/podcasts/episode/%5BpodcastEpisodeGuid%5D/page-e939c6b91b4a25d4.js"],"default"] 1f:T4ef,

Are your docs part of your DevOps cycle? Richard chats with Mattias Karlsson about automating documentation for APIs, cloud resources, and more! Mattias talks about using tools to build text files that contain every Azure resource being utilized, hopefully per application, along with API info, NuGet packages, and more. He also digs into the different audiences for that documentation - business wants to know what website exist, both interior and publically facing. Operations need to know what resources are consumed on-premises and in the cloud. Development is always looking for versions of APIs, calling approaches, etc. Maintaining documentation by hand is tedious and perpetually out-of-date. But if you can get up to speed with the tooling, you can make your documentation generate at the speed of deployment!

Links

Recorded October 29, 2024

20:T4d7,[{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Podcasts","item":"https://metacast.app/podcasts"},{"@type":"ListItem","position":2,"name":"Technology","item":"https://metacast.app/

‌

Episode description

DevOpsDocs with Mattias Karlsson

Episode description