Avoid raising errors on database passwords that contain a $
character
#14876
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes errors raised when a database password contains a
$
character by usingsafe_substitute
when templating. Templating will not occur when a$
character is present in the password, which means that errors may still occur with settings like the following:Since this setup would fail without these changes, and the docs recommend setting
PREFECT_API_DATABASE_CONNECTION_URL
directly, I think this behavior is acceptable.Closes #11067
Checklist
<link to issue>
"mint.json
.