We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Currently soft-delete for container registries is a preview feature that keeps deleted artifacts for a soft-delete interval.
Soft-delete allows accidental actions to be recovered to restore a service otherwise relying on the artifacts that have been deleted.
There are a number of limitations with the feature currently. See preview limitations.
As a result, we shouldn't recommend this feature if a retention policy is configured or if we know that the registry is geo-replicated.
The rule applies to the following:
CARML Update Docs Azure deployment reference
The text was updated successfully, but these errors were encountered:
@BernieWhite
Are you already working with this one? If not, I'd like to give it a try.
This is great news.
Sorry, something went wrong.
@bengeset96 No. Feel free to pick this one up.
BenjaminEngeset
Successfully merging a pull request may close this issue.
Rule request
Suggested rule change
Currently soft-delete for container registries is a preview feature that keeps deleted artifacts for a soft-delete interval.
Soft-delete allows accidental actions to be recovered to restore a service otherwise relying on the artifacts that have been deleted.
There are a number of limitations with the feature currently. See preview limitations.
As a result, we shouldn't recommend this feature if a retention policy is configured or if we know that the registry is geo-replicated.
Applies to the following
The rule applies to the following:
Additional context
CARML
Update
Docs
Azure deployment reference
The text was updated successfully, but these errors were encountered: