(1st MR) Refactorings to prepare to add a Logger
Preparing for: https://gitlab.com/gitlab-org/cells/http-router/-/issues/18
This was extracted from the (2nd MR) !205 (merged)
Context in this conversation: !205 (comment 2078617851)
What has been done in this MR?
-
.gitignore
ingwrangler.toml
because it's generated by GDK, which makes it show up in thegit diff
. The original file content has been copied towrangler.toml.example
instead. - Moving all the classify logic into
classify.ts
- Moving the main rules matching into a new class
RouterEngine
that can encapsulate all the logic of rules matching and applying the matching rule. And keeping the main part of the Router minimalexport default
. - Adding unique ID to the rules, so that we log which rule has been matched. Maybe we can add a validation that the IDs of the rules are unique in a follow up issue?
- Refactor the Documentation. Moved the development into its own page and added Blueprint relevant pages.
Validate changes
On both values GITLAB_RULES_CONFIG=passthrough
& GITLAB_RULES_CONFIG=firstcell
in your wrangler.toml
in env.dev
section, the Router should still forward requests to the GitLab instance. By visiting http://gdk.test:3000 you should still see GitLab running.
Merge request reports
Activity
assigned to @OmarQunsulGitlab
- Resolved by 🤖 GitLab Bot 🤖
Proper labels assigned to this merge request. Please ignore me.
@OmarQunsulGitlab
- please see the following guidance and update this merge request.1 Error Please add typebug typefeature, or typemaintenance label to this merge request. Edited by 🤖 GitLab Bot 🤖
added Category:Cell label
added devopsdata stores grouptenant scale sectioncore platform labels
changed milestone to %17.4
added maintenancerefactor label
added typemaintenance label
requested review from @bmarjanovic
mentioned in merge request !205 (merged)
- Resolved by Bojan Marjanovic
@bmarjanovic as you suggested here, I have extracted the changes not related to the Logger in this MR.
I suggest that you can see the final version of index.ts, because it might give you an idea how it would look like if this MR is merged.
- Resolved by Bojan Marjanovic
- Resolved by Bojan Marjanovic
- Resolved by Bojan Marjanovic
requested review from @tkuah and removed review request for @bmarjanovic
mentioned in merge request !218 (merged)
- Resolved by Bojan Marjanovic
- Resolved by Lin Jen-Shin
Thanks @OmarQunsulGitlab - I only have one question / concern
removed review request for @tkuah
mentioned in merge request gitlab-com/gl-infra/cells/http-router-deployer!9 (closed)
mentioned in merge request !225 (closed)
added 12 commits
-
37445d98...94459410 - 11 commits from branch
main
- 996ca581 - Refactorings to prepare to add a Logger
-
37445d98...94459410 - 11 commits from branch
reset approvals from @bmarjanovic by pushing to the branch
requested review from @bmarjanovic
mentioned in commit bda080ec
- Resolved by Bojan Marjanovic
A pipeline is running on a mirror related to this merge request.
Status: starting
https://ops.gitlab.net/gitlab-org/cells/http-router/-/pipelines/3665182
mentioned in merge request !230 (merged)
mentioned in merge request gitlab-org/gitlab-development-kit!4001 (merged)
mentioned in merge request !233 (merged)
added devopstenant scale groupcells infrastructure sectioninfrastructure platforms labels and removed devopsdata stores grouptenant scale [DEPRECATED] sectioncore platform labels