Practical Platform Engineering in 5 Lunches: 3. Pushing Template Changes

Part 3 of the blog series "Practical Platform Engineering in 5 Lunches" focuses on modifying and publishing changes to a shared process template within Platform Hub using Octopus Deploy. The post guides readers through updating a Platform PreDeploy Hook process template by committing changes to Git, emphasizing Git-based workflows for managing these modifications. The workflow uses the SemVer versioning scheme to classify changes as major, minor, or patch, and in this instance, a patch update ensures non-breaking changes that are automatically applied to the K8s Web App project. The series highlights the importance of an Internal Developer Platform (IDP) for scaling architectural decisions across projects, leveraging existing CI/ CD platforms, and supporting platform teams in managing and distributing shared templates. The series is 60% complete, with the next entry set to focus on structuring process templates to support multiple teams involved in different parts of the deployment process.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.