Expose Enabled Replication to API
Problem
This is a follow-up for this discussion thread: #13309 (comment 313972662)
Currently in the UI Geo Nodes are not aware if a replication options is enabled/disabled. We currently just show 0 items synced, however there is no current distinction between 0 synced and disabled.
In the above Issue the overall goal is to create that distinction
What does this MR do?
This creates a method on BaseRegistry
that defaults to a sync being enabled.
Then all inheriting Registries have the option to override the method and add logic to check if that particular replication is enabled.
Along with that, this MR also exposes that information to the API so that we can consume it on the UI to close out the above issue in a separate MR.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability 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 -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
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