Actions
Enhancement #22333
closed
Avoid sync group when importing a rule archive
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Effort required:
Name check:
To do
Fix check:
To do
Regression:
No
Description
Related to #21247, we would like to be able to avoid sync the group part or rules when importing, to accomodate to the case where we sync things between two environments.
This would work by using the Rule ID as merge identifier (ie, only do that for an imported rule for which there is already a rule with same id in current rudder).
It could also be done for directives, but there, the merge logic is more complex and the use case less needed => can be done in a second time.
Updated by François ARMAND about 1 year ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND about 1 year ago
- Related to User story #21247: Add an API endpoint to export rules, directives, techniques, groups and their dependencies in an archive added
Updated by François ARMAND about 1 year ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/4651
Updated by François ARMAND about 1 year ago
- Related to Enhancement #22342: Add a "all" keyword for export API in place of listing UUIDs of rule/directive/etc added
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.3.0~beta1 to 7.3.0~rc1
Updated by Anonymous about 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|cb744abee5d7bb193d9154662f4fb486c14bfa0e.
Updated by Vincent MEMBRÉ about 1 year ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.3.0~rc1 which was released today.
Updated by François ARMAND 3 months ago
- Related to Enhancement #23998: Completly ignore source target of rules when importing an archive added
Actions