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.

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

RDSInstance doesn't set username in writeConnectionSecretToRef if you are importing an existing resource #1999

Closed
trystanleftwich opened this issue Feb 14, 2024 · 0 comments · Fixed by #2000
Labels
bug Something isn't working

Comments

@trystanleftwich
Copy link
Contributor

What happened?

If I import an existing RDSInstance that has been orphaned, the username in the writeConnectionSecret is never set because its only ever set in the create workflow.

How can we reproduce it?

Create an RDSInstance using

deletionPolicy: Orphan
writeConnectionSecretToRef:
  name: foobar
  namespace: foobar1
forProvider:
...
   masterUsername: foo
   masterPasswordSecretRef:
     key: pass
     name: secret
     namespace: secret
...    
connectionDetails:
    - fromConnectionSecretKey: endpoint
    - fromConnectionSecretKey: port
    - fromConnectionSecretKey: username
    - fromConnectionSecretKey: password

Delete the Secret/manifests

What environment did it happen in?

Crossplane version:
V0.46.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant