NO-JIRA: Move AdditionalAnnotations to pkg/operator/tlsartifact#2146
NO-JIRA: Move AdditionalAnnotations to pkg/operator/tlsartifact#2146sanchezl wants to merge 2 commits intoopenshift:masterfrom
Conversation
|
@sanchezl: This pull request explicitly references no jira issue. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
7bdfde1 to
de54bbd
Compare
de54bbd to
8cc05c8
Compare
Repos requiring
|
|
/test unit |
|
@sanchezl: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
|
/lgtm Thanks for calling out the consumer repos that need the import update. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: hasbro17, sanchezl The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Overview
Moves the
AdditionalAnnotationstype,Certificate*annotation constants, andNewTLSArtifactObjectMetahelper frompkg/operator/certrotationtopkg/operator/tlsartifact, and removes the backward-compatible aliases that were left behind inpkg/operator/certrotation/annotations.go.This avoids circular dependencies — these types are used by packages that have no relation to cert rotation and should not need to import it:
pkg/operator/resourcesynccontroller— CA bundle ConfigMap managementpkg/operator/csr— CSR-based certificate managementpkg/certs/cert-inspection— TLS registry analysisAll consumers now import
tlsartifactdirectly.