Please describe the new behavior that that will improve Egeria
Some of our coco pharma notebooks cannot be run multiple times, for example errors such as
OMAG-COMMON-409-001 Method createGovernanceService of service Governance Engine OMAS is not able to create an instance of type GovernanceActionService because parameter name qualifiedName is defined as a unique property and value provision-weekly-measurements-governance-action-service is not available for use
* The system is unable to process the request because the unique property for this new entity is not permitted either because it is a reserved value, or it is already in use.
* Retry the request with a different unique parameter name.
are typical -- ie an entity already exists with the same name
This can be confusing to someone running the notebooks and wanting to carefully walk through and understand Egeria's behaviour.
Alternatives
Possible fixes
Handle purely through documentation. Explain how to reset the environment, both in egeria-docs web text as well as notebooks themselves
ensure each notebook has a section to 'undo' what it's done
using generated names to add uniqueness (may not work in all cases ie servers - awkward)
Any Further Information?
By default Egeria uses the 'inmemory' repository. In this mode, restarting the egeria platforms will effectively reset the repository. The charts also support the graph repository (and we've discussed xtdb) in which case this will not reset them
Would you be prepared to be assigned this issue to work on?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.
Is there an existing issue for this?
Please describe the new behavior that that will improve Egeria
Some of our coco pharma notebooks cannot be run multiple times, for example errors such as
are typical -- ie an entity already exists with the same name
This can be confusing to someone running the notebooks and wanting to carefully walk through and understand Egeria's behaviour.
Alternatives
Possible fixes
Any Further Information?
By default Egeria uses the 'inmemory' repository. In this mode, restarting the egeria platforms will effectively reset the repository. The charts also support the graph repository (and we've discussed xtdb) in which case this will not reset them
Would you be prepared to be assigned this issue to work on?