Repository Profiles Do Not Ovewrite All Configurations
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Fix Released
|
Medium
|
Mitch Burton |
Bug Description
Repository Profiles in Landscape should be configurable such that only certain repository sources are enforced, without removing repository configurations not defined in the Landscape Repository Profile.
Current behavior: changing tags of the machine impacts which Repository Profile is associated with the machine, and the entire /etc/apt/
Desired behavior: they wish to keep 3rd party repository configurations, without losing these repository configurations when tags are changed, when Landscape Repository Profiles are applied. We are looking to implement a temporary/fast solution, and define a better long term solution in a separate Jira ticket in the Landscape Engineering backlog.
https:/ /github. com/canonical/ landscape- client/ commit/ 92121f46a677a07 f58b0bcc24140cf 99b9b32d4d