Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Orphan entities should be removed from catalog #103

Open
tumido opened this issue Sep 7, 2022 · 4 comments
Open

Orphan entities should be removed from catalog #103

tumido opened this issue Sep 7, 2022 · 4 comments
Assignees
@tumido
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@tumido
Copy link
Member

tumido commented Sep 7, 2022

Describe the problem

We strive for declarative catalog, therefore orphan resources should be cleaned up once they are orphaned from the repository.

Steps to reproduce the problem

  1. Remove entity from catalog
  2. Refresh catalog
  3. See orphaned resource
  4. Try removing it
  5. Request denied

Screenshots

image
@tumido tumido self-assigned this Sep 7, 2022
@tumido tumido mentioned this issue Sep 8, 2022
Merged
@SamoKopecky SamoKopecky added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 28, 2022
@sesheta
Copy link
Member

sesheta commented Dec 27, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 27, 2022
@SamoKopecky
Copy link
Member

/remove-lifecycle stale

@sesheta sesheta removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 3, 2023
@sesheta
Copy link
Member

sesheta commented Apr 3, 2023

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 3, 2023
@sesheta
Copy link
Member

sesheta commented May 3, 2023

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tumido tumido

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tumido @sesheta @SamoKopecky