New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCPCLOUD-2563: Add Machine/MachineSet API for MAPI to CAPI migration #1818
Changes from all commits
8496052
3fd6a5c
f04d80b
02673f4
8f5c774
6a61988
ce87825
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,6 +20,7 @@ type AWSResourceReference struct { | |
ARN *string `json:"arn,omitempty"` | ||
// Filters is a set of filters used to identify a resource. | ||
// +optional | ||
// +listType=atomic | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not familiar with this type of list, what does it do? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Atomic lists are updated as a unit. This is actually the default behaviour when specified, hence, in most cases, the correct thing to do for backward compat is to set the default explicitly. The alternatives are map and set, maps I believe you've seen before, and sets are problematic, so we avoid them |
||
Filters *[]AWSResourceFilter `json:"filters,omitempty"` | ||
} | ||
|
||
|
@@ -45,5 +46,6 @@ type AWSResourceFilter struct { | |
Name string `json:"name"` | ||
// Values includes one or more filter values. Filter values are case-sensitive. | ||
// +optional | ||
// +listType=atomic | ||
Values []string `json:"values,omitempty"` | ||
} |
Large diffs are not rendered by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
intentionally never enabled?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. As this is greenfield, there's a lot to build before we have something that works. My hope was that we can get this all set up to a point where there's actually something tangible before adding to a feature set some time in 4.17