Geo Nodes Beta - Remove "Beta"
What does this MR do?
This MR is a step required before we can remove the :geo_nodes_beta Feature Flag #296986 (closed).
Currently the UI is leveraging an /admin/geo/nodes and /admin/geo/nodes_beta route to test the new UI without obstructing the current UI. This change removes the separate routes and instead returns to a typical Feature Flag approach where we render one UI or the other based on the FF.
This will allow us to now remove the legacy code and FF in a follow up MR and be sure that everything is in place and isolate any issues that result from the cutover.
This change is also behind a feature flag (:geo_nodes:beta)
How to test
- Set up a Geo Primary/Secondary GDK
- Fetch the current branch
- Activate the Feature Flag on your Primary GDK (
:geo_nodes_beta) - Navigate to
http://127.0.0.1:3000/admin/geo/nodes_beta - View UI
Screenshots (strongly suggested)
| No FF | FF |
|---|---|
 |
 |
Does this MR meet the acceptance criteria?
Conformity
-
I have included a changelog entry, or it's not needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. - [-] I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
- [-] 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 to #296986 (closed)