[Epic] Provide delete Python package index endpoint

[fridex]

Is your feature request related to a problem? Please describe.

As Thoth operator, I would like to have the ability to remove Python package index from Thoth deployment. As of now, I am able to disable an index, but it might be nice to also provide an ability to delete a Python package index and all the packages associated with it (decommission of an index).

Describe the solution you'd like

Create an endpoint for deleting a Python package index. This endpoint will trigger a workflow that will be responsible for deleting a Python package index. The async workflow handling is required as there might be associated thousands of packages with an index (it will require a lot of time to delete data from the database).

Additional context:

• Knowledge of management-api
• knowledge of thoth-storages for deleting the python package index using cascade method.
• research on metrics that would need changes based on this.

Acceptance criteria

• create an endpoint in management-api.
• create truncate function for python package index in storages.
• investigate which metrics needs update
• implement the metrics changes
• verify the whole feature.

[goern]

/triage accepted
/priority important-longterm
/kind feature

[sesheta]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sesheta]

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

[fridex]

/remove-lifecycle rotten
/triage accepted

[goern]

/sig devsecops
/priority backlog
/remove-priority important-longterm

[harshad16]

/sig stack-guidance

[mayaCostantini]

/good-first-issue

[sesheta]

@mayaCostantini:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mayaCostantini]

As discussed during the SIG Stack Guidance meeting,
/assign @VannTen

[VannTen]

Regarding the two points concernings metrics, I'm not sure there is anything to
do (once the rest works).

AFAICT, this would affect metrics from the thoth-station/metrics-exporter (which
mostly translaste to DB/storages queries, if I'm not mistaken). But a quick look
don't reveal metrics depending on a particular index (nor should they).