Move all Cloud Connector code under `::CloudConnector`
What does this MR do and why?
We're currently maintaining Cloud Connector code under two distinct namespaces:
::CloudConnector::Gitlab::CloudConnector
I don't think there was a hard and fast rule where code should be filed when we first added it, but we found in !172705 (comment 2222656897) that maintaining code in Gitlab::CloudConnector in both the monolith and the gitlab-cloud-connector gem leads to load path issues.
We therefore decided to:
- Move all Cloud Connector code in the monolith into
::CloudConnector - Move all Cloud Connector code in gitlab-cloud-connector into
Gitlab::CloudConnector(that's already the case anyway)
The two remaining classes in Gitlab::CloudConnector will either be removed or move into the library after !172705 (merged) is fully rolled out.
This is a refactor and not user facing.
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.