Switching off artifacts

[tostt]

Does your feature request solve a problem? Please describe.
A useful Harbor feature would be the ability to deactivate specific artifacts. In organizations with a large number of artifacts, especially those that are regularly decommissioned, there is a risk of accidentally deleting artifacts that may still be needed. Deactivating artifacts would allow them to be effectively hidden or removed from active use before permanently deleting them.

Describe the solution you'd like to see
Provide project maintainers with the ability to deactivate any artifact within their project. Deactivated artifacts would be ignored by all Harbor functions, and only users with "project maintainer" privileges or higher would be able to either reactivate or delete them.

Describe the main design/architecture of your solution
Each artifact could have a boolean field (e.g., "isActive") to indicate its active status. A toggle button in the GUI would allow users to change the artifact's state between "active" and "inactive." When responding to Docker commands or API calls, Harbor should return an appropriate error message indicating that the artifact is inactive.

[bupd]

I think there is some policy option in harbor. Which you can use to make images not deployable. Let me check. 👀

[Vad1mo]

The requirements are not clear. Please provide a more in-depth analysis going over what each user and robot account is allowed to do.

[tostt]

Thank you for your response. Here are more details about adding an active status to artifacts.

Artifact status change
Users and robot accounts that have the "Delete artifact" permission would additionally be able to change the "active" status of artifacts. The reason for suggesting the "Delete artifact" permission is that deactivating an artifact is similar to deleting it — but not for real.

Artifact status filter
The active/inactive status can be seen (and possibly implemented) as a boolean-dependent filter on the artifact list. When a user or robot account performs an action involving an artifact (whether using the GUI, a docker command, or an API call), Harbor would filter out inactive artifacts.

Default artifact status
When pushed to Harbor, all artifacts would be marked as "active" by default.

Error message consideration
Earlier I mentioned creating a custom error message, but, thinking more about it, I believe it's better not to change anything. Users who cannot see inactive artifacts will receive the standard message for artifacts that do not exist.