Skip to content

Conversation

@dagguh
Copy link

@dagguh dagguh commented Jan 11, 2022

No description provided.

If we'll need to change the "encryption method" SQL without changing the
"update password" SQL, then we can think about reintroducing some
indirection.
Right now it relies on passing the same `SshSqlClient`, the same schema
name, and it creates more areas for mistakes than it saves by the
decoupling.
If the detection SQL is really problematic, then consumers can write their own
`JiraUserPasswordOverridingDatabase` to opt-out short term.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant