Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement export/import of entity configurations #858

Closed
hlayisanimazuze opened this issue Jan 10, 2024 · 3 comments
Closed

Implement export/import of entity configurations #858

hlayisanimazuze opened this issue Jan 10, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request ready for testing

Comments

@hlayisanimazuze
Copy link
Collaborator

  1. Generic export and import should include entity configurations. I've implemented base classes and UI, but we need to implement configuration versioning and export/import rules for entity configs.
  2. Documentation about the export/import available here.
  3. Some technical details:
  • Back-end:
    • ConfigurationItemAppService - application service that work with packages, it allows to export/import and analyze package, works with registered exporters and importers.
    • EntityConfigExport - class that implements export of entity configs, it's already registered and works, but maybe you'll have to make changes in the exported data/format
    • EntityConfigImport - class that implements import of entity configs. It's registered but doesn't contain implementation of the import. Here you need to implement the logic
  • Front-end:
    • Dialogs for export and import support configuration items of any type but currently they show only forms. You'll need to uncomment this GQL filter to unlock other types of configuration items, check this file: src\components\configurationFramework\itemsExport\index.tsx

image

NOTE: export/import functionality should take into account the versioning of configs and EntityConfigsBootstrapper. There should be transparent limitations and rules of the entity config lifecycle.

@hlayisanimazuze hlayisanimazuze added the enhancement New feature or request label Jan 10, 2024
@hlayisanimazuze hlayisanimazuze added this to the Backlog milestone Jan 10, 2024
@hlayisanimazuze
Copy link
Collaborator Author

hlayisanimazuze commented Feb 5, 2024

Note: When implementing this item, please ensure that an implementation is in place to prevent configurations (e.g., formatting) from resetting to their original values if the entity changes in the code. This comment is in support for this item #757

@hlayisanimazuze
Copy link
Collaborator Author

Hi @AlexStepantsov , we've prioritise this item in this current implementation

@AlexStepantsov
Copy link
Contributor

AlexStepantsov commented Feb 17, 2024

Import/export are implemented.
Implementation is prevent configurations (e.g., formatting) from resetting to their original values if the entity changes in the code. But note that hardcoded attributes have high priority, replace configured values and Entity Configurator doesn't allow to change them

Implementation versioning of entity configurations moved to separate issue #1075
For now import updates current version of EnittyConfig.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ready for testing
Projects
None yet
Development

No branches or pull requests

2 participants