Change Master/Slave Language to Primary/Replica

• So that the terminology used in MaxScale is more inclusive and up-to-date,
• As a MaxScale user,
• I want the language in MaxScale to change from master/slave to primary/replica.

Acceptance Test - Update Terminology in Configuration Files

• Given a MaxScale configuration file using master/slave terminology
• When I update MaxScale to the new version
• Then the configuration file recognizes and supports the terms primary/replica instead of master/slave
• And MaxScale operates correctly using the new terminology

Acceptance Test - Backward Compatibility with Master/Slave Terminology

• Given a MaxScale configuration file using master/slave terminology
• When I update MaxScale to the new version
• Then the configuration file continues to recognize and support the terms master/slave
• And MaxScale operates correctly using the old terminology
• And a warning is logged suggesting updating the terminology to primary/replica

Acceptance Test - Updated Terminology in User Interface

• Given I am accessing the MaxScale user interface
• When I navigate to sections displaying replication settings and status
• Then all instances of master/slave are replaced with primary/replica
• And the functionality remains the same

Acceptance Test - Documentation Update

• Given I am reading MaxScale documentation
• When I look up replication-related topics
• Then all references to master/slave are replaced with primary/replica
• And the instructions and examples use the new terminology

Acceptance Test - Logging and Error Messages

• Given MaxScale logs and error messages
• When a replication-related event occurs
• Then the log and error messages use the terms primary/replica instead of master/slave
• And the content and clarity of the messages are maintained