Project

General

Profile

Actions

User story #5738

closed

Export and import (create, update) Rule with all dependencies

Added by François ARMAND about 10 years ago. Updated about 1 year ago.

Status:
Resolved
Priority:
3
Assignee:
-
Category:
Web - Config management
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
No

Description

The API allows to get rules, but not with all the groups/directives/parameters used in them. So it's a real burden to import it back in one other Rudder instance.

The ideal scenario would be:

- I can "export" a Rule with all its context (directives, groups, parameters used in directives) and get a JSON file with all the content
- the export is a get "full" on the API, but there is also a "export" button on Rule screen

The "import" part is more tricky, because we have to ask the user how he wants to manage the create/update of the rules and all subparts:

- the import is available either with an API call or via a button on the Rules screen
- on import, look for a rule with the same name or the same UUID
- if none exists, propose to create. Else, ask if the user want to create a new one (with new name) of update the existing one
- also ask if the user want to also import exactly use Directives AND/OR Groups AND/OR parameters of the imported rules, or if he only want to update somes.
- ideally, the user see a diff for each part, so that he knows exactly what is different between the imported rules and the existing one, like what is shown in change request


Related issues 2 (0 open2 closed)

Related to Rudder - Bug #7396: Archive everything does not archive everythingRejectedNicolas CHARLESActions
Related to Rudder - User story #21247: Add an API endpoint to export rules, directives, techniques, groups and their dependencies in an archiveReleasedActions
Actions #1

Updated by François ARMAND about 10 years ago

  • Subject changed from Get and create/update Rule with all dependencies via API to Export and import (create, update) Rule with all dependencies
Actions #2

Updated by François ARMAND about 10 years ago

Remark: a prototype of the API could be done in a plugin, which will allow a better iterative dev cycle

Actions #3

Updated by Benoît PECCATTE almost 10 years ago

That could be useful for synchronization.
While waiting for this API to come to existence, a workaround could be coded in a client library.

Actions #4

Updated by Benoît PECCATTE over 8 years ago

  • Target version set to Ideas (not version specific)
Actions #5

Updated by François ARMAND over 8 years ago

  • Related to Bug #7396: Archive everything does not archive everything added
Actions #6

Updated by François ARMAND about 1 year ago

  • Status changed from New to Resolved
  • Regression set to No

This is done in #21247

Actions #7

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
Actions

Also available in: Atom PDF