Destination in Sequence#2094
Conversation
This reverts commit e85e7a8.
| fe.Details = "only name, apiVersion and kind are supported fields" | ||
| return fe | ||
| }(), | ||
| // TODO current destination ref allows setting the namespace, thus this fails. |
There was a problem hiding this comment.
/hold
we have a DeprecatedNamespace in Destination, is that correct? I thought we weren't supporting namespaces in ObjectRef..
If that is the case, the Ref in Destination should actually validate that... as done here
There was a problem hiding this comment.
/hold cancel, it seems that we will let this through
|
/assign @vaikas-google |
|
The following is the coverage report on the affected files.
|
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nachocano, vaikas-google 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 |
Harwayne
left a comment
There was a problem hiding this comment.
Looks great so far, but I think it needs to also:
- Add OpenAPI schema for the field.
- Add a deprecation warning to the object's status if the old fields are used.
- Remove the deprecation warning from the object's status if the old fields are no longer used.
Adam, this changes actually got in with #2095... The parallel branch was forked from here. In both I didn't do this... Let me add it and will submit a new PR... Might be ready by Monday. Will close this one... |
Proposed Changes
Release Note