generate-borgmatic-config with source file does not upgrade Healthchecks schema #536

Closed
opened 2022-05-25 17:20:37 +00:00 by witten · 2 comments
Owner

What I'm trying to do and why

I'm trying to upgrade a borgmatic 1.6.0 configuration file containing Healthchecks settings to borgmatic 1.6.1.

Steps to reproduce

generate-borgmatic-config -s 1.6.0.yaml -d 1.6.1.yaml

Actual behavior

The Healthchecks configuration in the generated file stays as the old-style scalar:

hooks:
    healthchecks: https://...

Expected behavior

I expect the configuration to get upgraded to the new-style object mapping with multiple options:

hooks:
    healthchecks:
        ping_url: https://...
        # send_logs: false
        ...

Other notes / implementation ideas

The problem is that the generation code doesn't call the normalize() function to "upgrade" the source configuration's schema.

Environment

borgmatic version: 1.6.1

borgmatic installation method: pip install --editable

Borg version: 1.2.0

Python version: 3.10.4

operating system and version: Manjaro stable

#### What I'm trying to do and why I'm trying to upgrade a borgmatic 1.6.0 configuration file containing Healthchecks settings to borgmatic 1.6.1. #### Steps to reproduce `generate-borgmatic-config -s 1.6.0.yaml -d 1.6.1.yaml` #### Actual behavior The Healthchecks configuration in the generated file stays as the old-style scalar: ``` hooks: healthchecks: https://... ``` #### Expected behavior I expect the configuration to get upgraded to the new-style object mapping with multiple options: ``` hooks: healthchecks: ping_url: https://... # send_logs: false ... ``` #### Other notes / implementation ideas The problem is that the generation code doesn't call the normalize() function to "upgrade" the source configuration's schema. #### Environment **borgmatic version:** 1.6.1 **borgmatic installation method:** `pip install --editable` **Borg version:** 1.2.0 **Python version:** 3.10.4 **operating system and version:** Manjaro stable
witten added the
bug
label 2022-05-25 17:20:43 +00:00
Author
Owner

Fixed in master.

Fixed in master.
Author
Owner

This fix has been released in borgmatic 1.6.2!

This fix has been released in borgmatic 1.6.2!
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#536
No description provided.