Create subscriber.uri and deprecate subscriber.dnsName#994
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Harwayne The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| // http://myexternalhandler.example.com/foo/bar | ||
| // +optional | ||
| DNSName *string `json:"dnsName,omitempty"` | ||
| DeprecatedDNSName *string `json:"dnsName,omitempty"` |
There was a problem hiding this comment.
when will it be removed? the DeprecatedDNSName ?
There was a problem hiding this comment.
#993 tracks removing it. The plan is to leave it deprecated for one release. Then remove it in the next. So if this PR merges into 0.5.0, we would remove it in 0.6.0.
| fieldsSet = append(fieldsSet, "ref") | ||
| } | ||
| if s.DeprecatedDNSName != nil && *s.DeprecatedDNSName != "" { | ||
| fieldsSet = append(fieldsSet, "dnsName") |
There was a problem hiding this comment.
My hesitation for doing that is code like our Trigger controller, which will compare the spec, if it differs, it will delete the Subscription and create a new one. Our Trigger controller wouldn't hit that problem because it uses ref, not dnsName, but I could see a similar controller hitting the problem.
What do you think? Is it worth the potential trouble to move things for the user?
There was a problem hiding this comment.
ok, fair point w/ the Trigger controller.
So, no need to "adjust" it
|
The following is the coverage report on pkg/.
|
|
/lgtm |
[release-v1.16] Update golang.org/x/net to 0.34.0
Fixes #991
Proposed Changes
subscriber.uriand deprecatesubscriber.dnsName.subscriber.dnsNamefield.Release Note