Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reset passwords when the ones set in secret change #75

Open
calind opened this issue Jun 20, 2018 · 5 comments
Open

Reset passwords when the ones set in secret change #75

calind opened this issue Jun 20, 2018 · 5 comments
Labels
enhancement

Comments

@calind
Copy link
Member

calind commented Jun 20, 2018

No description provided.

@calind calind mentioned this issue Jun 20, 2018
Closed
@calind calind added this to the Production level milestone Jun 25, 2018
@calind calind modified the milestones: Production level, 0.2.x Jul 17, 2018
@AMecea AMecea changed the title Reset passowords when the ones set in secret change Reset passwords when the ones set in secret change Feb 13, 2019
@AMecea AMecea mentioned this issue Feb 13, 2019
Closed
calind added a commit to bitpoke/stack that referenced this issue Feb 15, 2019
@calind
Workaround for bitpoke/mysql-operator#75
2abf343
@AMecea AMecea modified the milestones: 0.2.x, 0.2.6 Feb 25, 2019
@AMecea
Copy link
Contributor

AMecea commented Feb 25, 2019

Depends on #240

@AMecea AMecea modified the milestones: 0.2.6, 0.2.x Mar 12, 2019
@AMecea
Copy link
Contributor

AMecea commented Mar 20, 2019

Depends on #259

@AMecea AMecea modified the milestones: 0.2.x, 0.3.x Mar 20, 2019
@AMecea AMecea modified the milestones: 0.3.x, 0.5.x Apr 2, 2019
@marratj
Copy link
Contributor

marratj commented Jul 8, 2019

Hi,

is there a timeline for when this might be implemented?

This would also be a very convenient feature for Clusters that have been initialized from a backup, because after being restored from the backup, the credentials of the cluster obviously also don't match with the ones from the secret.

Especially for quickly cloning environments or restoring from backups without the need to externally store the credentials for the database this would be very handy to have implemented.

Is there anything we can help with on that front?

@benosman
Copy link

benosman commented Sep 5, 2019

Likewise, I would like this functionality especially when restoring from backups.

@AMecea AMecea mentioned this issue Oct 26, 2020
Open
@calind calind removed this from the 0.5.x milestone Oct 11, 2021
@elrondwong
Copy link

It is also important to change the secret password key after password has changed by the mysql client.

chapsuk pushed a commit to chapsuk/mysql-operator that referenced this issue Oct 16, 2023
@enisoc
Add option to configure storage endpoint for AWS (bitpoke#75)
269e09d 
* Add option to configure storage endpoint for AWS

Signed-off-by: Dan Kozlowski <koz@planetscale.com>

* Generating Documentation

Signed-off-by: Dan Kozlowski <koz@planetscale.com>

* Updates to CRDs

Generating Documentation

Co-Authored-By: Anthony Yeh <enisoc@planetscale.com>
Co-Authored-By: Anthony Yeh <enisoc@planetscale.com>
Signed-off-by: Dan Kozlowski <koz@planetscale.com>

Co-authored-by: Anthony Yeh <enisoc@planetscale.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@calind @benosman @marratj @elrondwong @AMecea