Details

    • Similar Issues:
      Show 10 results 

      Description

      The deployment repository is only loosely coupled to the domain model; i.e. users can add content to the repo and then have a problem or decide to not execute a deployment plan with the result that the deployment is not used in the model. Or they can remove the deployment from the model via an update, which doesn't remove it from the repo (in case the update needs to be rolled back.)

      Effect of this is unreferenced deployment content can accumulate in the repo, so we need a gc utility that can be used to clean it out.

        Issue Links

          Activity

          Hide
          Brian Stansberry
          added a comment -

          First step would be an operation on the root resource for a domain or a standalone server to allow a user to manually trigger this.

          Show
          Brian Stansberry
          added a comment - First step would be an operation on the root resource for a domain or a standalone server to allow a user to manually trigger this.
          Hide
          Brian Stansberry
          added a comment -

          Ignore the comment above; the resolution to this issue did not involve a manual operation.

          Show
          Brian Stansberry
          added a comment - Ignore the comment above; the resolution to this issue did not involve a manual operation.

            People

            • Assignee:
              Kabir Khan
              Reporter:
              Brian Stansberry
            • Votes:
              6 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: