fix: wrong pico_service password + picodata expel --user
Summary
- fix: used to not provide pico_service password on initial replication configuration
- test: now conftest.Cluster.deploy sets the non-empty pico_service password for the cluster
- fix:
picodata expel
now accepts --user, --password-file & --auth-method parameters and behaves the same waypicodata connect
does with respect to credentials
Note that using picodata expel
requires providing a user which is authorized to execute stored procedure .proc_expel_redirect
. Currently by default the only such user is pico_service
and the only way to create another user with such privileges is to go through lua.
- Close #...
- Target branch: master
- Changes should be cherry-picked to 24.1: yes / no
- Docs follow-up: docs#199 (closed)
Edited by Georgy Moshkin
Merge request reports
Activity
assigned to @gmoshkin
added 8 commits
-
5f49d16b...3521184b - 2 commits from branch
master
- 5320f8ca - chore: clippy warning
- 71466ccf - test: run integration tests with non-empty pico_service password by default
- 6f6cc7b6 - fix: used to not provide pico_service password on initial replication configuration
- 73909233 - refactor: cleanup picodata connect code
- 077f96d3 - fix: Error::ClusterIdMismatch error message was wrong when expelling
- 7c5c744c - fix: picodata expel add --user --password-file & --auth-method parameters
Toggle commit list-
5f49d16b...3521184b - 2 commits from branch
requested review from @rosik
added 8 commits
-
7c5c744c...a3f71d6f - 3 commits from branch
master
- cadcb4e3 - test: run integration tests with non-empty pico_service password by default
- 255ae9e0 - fix: used to not provide pico_service password on initial replication configuration
- b38aed64 - refactor: cleanup picodata connect code
- dca4eaa0 - fix: Error::ClusterIdMismatch error message was wrong when expelling
- 8ebb6428 - fix: picodata expel add --user --password-file & --auth-method parameters
Toggle commit list-
7c5c744c...a3f71d6f - 3 commits from branch
enabled an automatic merge when the pipeline for 8ebb6428 succeeds
mentioned in issue docs#199 (closed)
mentioned in issue #496 (closed)
Please register or sign in to reply