Petals Registry Overlay

Only delete topologies (and their endpoints) when they don't have any containers in them anymore

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0.1
  • Fix Version/s: 1.0.2
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    Currently, topologies are deleted when no clients are connected to them but this contradicts with PETALSESBCONT-417.

    This means that:

    • we should only remove topologies when they are emptied of their containers.
    • we never remove static topologies and that it becomes an admin operation to do so (for example, using the Petals Registry CLI command 'delete-topology')
    Show
    Currently, topologies are deleted when no clients are connected to them but this contradicts with PETALSESBCONT-417. This means that:
    • we should only remove topologies when they are emptied of their containers.
    • we never remove static topologies and that it becomes an admin operation to do so (for example, using the Petals Registry CLI command 'delete-topology')
  • Environment:
    -

Issue Links

Depends
 

Activity

People

Dates

  • Created:
    Fri, 20 May 2016 - 15:25:23 +0200
    Updated:
    Fri, 3 Jun 2016 - 17:43:55 +0200
    Resolved:
    Fri, 3 Jun 2016 - 17:43:55 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.