Skip to content

Conversation

@rdelaage
Copy link
Contributor

Hi!

This PR fix the regression introduced in #1577 by adding an opt-in flag for environment variable substitution in profile files. Users can still use $ in their file if they enable substitution by escaping them (\$).

This PR closes #1598 and #942

@aawsome aawsome changed the title Substitute environment variables in profiles only if explicitly opted-in fix: Substitute environment variables in profiles only if explicitly opted-in Nov 10, 2025
Copy link
Member

@aawsome aawsome left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks a lot for the fast PR @rdelaage

@aawsome aawsome enabled auto-merge November 10, 2025 13:13
@aawsome aawsome added this pull request to the merge queue Nov 10, 2025
Merged via the queue into rustic-rs:main with commit f0ddb47 Nov 10, 2025
30 checks passed
github-merge-queue bot pushed a commit that referenced this pull request Nov 11, 2025
## 🤖 New release

* `rustic-rs`: 0.10.1 -> 0.10.2 (✓ API compatible changes)

<details><summary><i><b>Changelog</b></i></summary><p>

<blockquote>

##
[0.10.2](v0.10.1...v0.10.2)
- 2025-11-10

### Fixed

- Substitute environment variables in profiles only if explicitly
opted-in ([#1600](#1600))
</blockquote>


</p></details>

---
This PR was generated with
[release-plz](https://github.com/release-plz/release-plz/).

Co-authored-by: rustic-release-plz[bot] <182542030+rustic-release-plz[bot]@users.noreply.github.com>
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.

Rustic 0.10.1 fatal parse error due to special characters in password.

2 participants