-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat: IAM Auth for RDS #3559
feat: IAM Auth for RDS #3559
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really like how these dependencies are leaking into user deployments, but that is not something we can solve now.
} | ||
|
||
authenticationToken, err := auth.BuildAuthToken( | ||
// TODO: proper region |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
!!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will be done very soon!
|
||
Username string `parser:"" protobuf:"2"` | ||
Endpoint string `parser:"" protobuf:"3"` | ||
Database string `parser:"" protobuf:"4"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't want this to be parseable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, that is just cargo culting from the existing runtime, and it seems to work. Not totally sure what this does. Should these be parseable?
Have not been yet fully test e2e, but at least this creates the user with right auth mechanism.
Merging this in will help testing, as I won't need to keep manual docker images in sync.