Uploaded image for project: 'Policy Framework'
  1. Policy Framework
  2. POLICY-4651

Extend instance deletion to request additional actions in participant

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • Montreal Release
    • None
    • clamp

      At the moment, when acm instances are undeployed, it is assumed that whatever resources the participant is using for that instance have been released through undeploy. Effectievly, this step removes the instance from the participants.

      After this, if instance deletion is triggered, the record of the instance is simply deleted from the database.

      This Jira will extend the functionality of this deletion step to also inform the participant of instance deletion. This will allow the participant to take any necessary steps that might result from instance deletion. For example, deletion of some records in a database that the participant communicates with.

      Implementation will involve the addition of more methods to the participant intermediary interfaces to be implemented by the participants. It will also likely involve additional states being added to the state machine e.g. DELETING

            FrancescoFioraEst Francesco Fiora
            saul.gill Saul Gill
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: