Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • feudalBackend feudalBackend
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • feudalfeudal
  • feudalBackendfeudalBackend
  • Issues
  • #73
Closed
Open
Issue created Jun 17, 2020 by lukas.burgey@af9063Owner

Make deregister remove all the clients deployments

The changes from #50 (closed) should be integrated with the deregister client call like so:

  • Client requests deregister
  • during the handling of the request the sites services are deleted (maybe also the site itself?)
  • the deletion causes DeploymentStates to be orphaned
  • Response should look like the response to a standard fetch by the client
  • the client handles this fetched data as usual (i.e. removing the deployments)
  • the client shuts down

This needs changes to the deregister view and the clients handling of the response obviously.

Edited Jun 17, 2020 by lukas.burgey
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking

Imprint