-
Given GitLab inventory builder is still in use at GitLab, and based on the commit history, still maintained, I've opened this MR to remove the deprecation notice. Inventory builder is still a useful tool with a lot of potential to incubate new functionality in GitLab, as well as build inventory of what users are shipping to their customers. There has been several times in the past where I've had ideas for new GitLab capabilities which would have made sense to test and validate by extending GitLab Inventory Builder, however the deprecation notice has suggested I shouldn't do that. A few examples of gaps I've been working on recently which I think would be very sensible additions to GitLab Inventory Builder to test & prove them out prior to building GitLab features are: * Policy validation of CI/CD configuration elements for images being built in project pipelines from a security perspective (i.e. things like base image updates being performed during build) * Image use and distribution cataloging for inventorying what we ship externally vs what we use internally, and ownership of those images * CI configuration baseline "starter packs" or frameworks and gap identification for container image scanning and composition So I think until we are not longer using and maintaining GitLab Inventory Builder, we should not mark it as deprecated. We don't currently have another tool which is building inventory for GitLab projects and this overarching goal is not currently possible in GitLab itself so I think there is still a lot of value here, and we should work to also properly extract any potential product gaps & contributions from this tooling prior to marking as deprecated.
Given GitLab inventory builder is still in use at GitLab, and based on the commit history, still maintained, I've opened this MR to remove the deprecation notice. Inventory builder is still a useful tool with a lot of potential to incubate new functionality in GitLab, as well as build inventory of what users are shipping to their customers. There has been several times in the past where I've had ideas for new GitLab capabilities which would have made sense to test and validate by extending GitLab Inventory Builder, however the deprecation notice has suggested I shouldn't do that. A few examples of gaps I've been working on recently which I think would be very sensible additions to GitLab Inventory Builder to test & prove them out prior to building GitLab features are: * Policy validation of CI/CD configuration elements for images being built in project pipelines from a security perspective (i.e. things like base image updates being performed during build) * Image use and distribution cataloging for inventorying what we ship externally vs what we use internally, and ownership of those images * CI configuration baseline "starter packs" or frameworks and gap identification for container image scanning and composition So I think until we are not longer using and maintaining GitLab Inventory Builder, we should not mark it as deprecated. We don't currently have another tool which is building inventory for GitLab projects and this overarching goal is not currently possible in GitLab itself so I think there is still a lot of value here, and we should work to also properly extract any potential product gaps & contributions from this tooling prior to marking as deprecated.
Loading