Use root-enable in redis to enable authentication
Root-enable and root-disable are two common commands in Trove to enable/disable root for database like mysql. But when we come to redis, it seems that we can only enable/disable authentication by using configuration group because there is no root-enable/
I would like to implement a bp that using root-enable/
1. enable/disable authentication for single redis instance;
2. enable/disable authentication for replica instances. For example, when we create a replica instance of a exist single redis instance, and then we do root-enable in master node, the slave node should be also enabled authentication. When we have single redis instance which has already authentication enabled, then we create a replica instance of it, the replica instance has enabled authentication which I have tested in trove version newton. So in this patch, we won't discuss about this scenario.
But here we have another problem, what if we do root-enable to enable authentication and then the customer removes it by using configuration group? I think we should discuss about it. My advice is that we can remove requirepass item in validation-
Blueprint information
Whiteboard
Implement root-enable/
Specification: https:/
Gerrit topic: https:/
Addressed by: https:/
Implementation of root-enable, root-disable in redis.
Work Items
Work items:
Development of this implementation: DONE
Test locally for single redis instance: DONE
Test locally about doing root-enable for master instance in replication after the slave being created: DONE
Test locally about doing root-enable for master instance in replication before creating slave instance. When we have done root-enable in master, then create slave instance, it seems that after the slave's status is ACTIVE, it does not write requirepass and masterauth into /etc/redis.conf like I said above in description. Still need further investigation. I am going to finish the unit test first: DONE
Complete unit tests: DONE
Review: DONE