Create Conan package file metadata table to match EE
What does this MR do?
This is the migration for the Conan metadata table to be used by the Conan package registry being implemented for https://gitlab.com/gitlab-org/gitlab-ee/issues/8248. The EE MR is https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/16466.
The metadata is meant to hold the Conan specific information for a given package file. This includes the Conan "recipe", the partial file "path" that is used to construct urls used by the Conan CLI, and the package file "revision", which is a placeholder for now defaulting to "0". The Conan CLI expects a revision of "0" when v1 of the conan api is used, eventually we may implement v2, which will make heavier use of this column.
Questions for the reviewer:
- This is my first migration MR since joining GitLab, it's my understanding that both CE and EE require an MR for the migration to keep both schemas in sync. I followed the instructions from the CI error in this MR to create the EE MR.
- Does this MR need a changelog since it will be mirrored in EE and the functionality will live in EE?
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry for user-facing changes, or community contribution. Check the link for other scenarios. -
Documentation created/updated or follow-up review issue created -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Performance and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related #67095 (moved), https://gitlab.com/gitlab-org/gitlab-ee/issues/8248