-
Notifications
You must be signed in to change notification settings - Fork 553
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
raft autopilot updates #1705
raft autopilot updates #1705
Conversation
5be4f18
to
445b004
Compare
internal/consts/consts.go
Outdated
FieldGroupName = "group_name" | ||
FieldExternal = "external" | ||
FieldInternal = "internal" | ||
FieldAPIHostname = "api_hostname" |
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.
These have been sorted. I thought it might be ok do so since I was adding fields that were changing the indent level for all entries. However, I am beginning to doubt the value in doing this as it could make rebasing on top of this quite annoying.
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.
Hmm that is definitely a valid point! I'm now wondering if it's better to leave these unsorted and as they were for now, and we can decide on the benefits of sorting once we have finished updating all resources/datasources to use field constants — something we are tracking for long term sustainability of this project which will add to this list a lot. Might be worth adding all the constants and then sorting them in one go. What do you think?
156af32
to
b9a572c
Compare
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.
PR's looking great! Thanks for adding these 🙏🏼
internal/consts/consts.go
Outdated
FieldGroupName = "group_name" | ||
FieldExternal = "external" | ||
FieldInternal = "internal" | ||
FieldAPIHostname = "api_hostname" |
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.
Hmm that is definitely a valid point! I'm now wondering if it's better to leave these unsorted and as they were for now, and we can decide on the benefits of sorting once we have finished updating all resources/datasources to use field constants — something we are tracking for long term sustainability of this project which will add to this list a lot. Might be worth adding all the constants and then sorting them in one go. What do you think?
|
||
// serializeFields is a map of fields that have complex structures that we will | ||
// serialize for convenience instead of defining the schema explicitly | ||
var serializeFields = map[string]string{ |
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.
Nice!
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.
LGTM!
This PR adds a new field
disable_upgrade_migration
to the Raft autopilot resource. Additionally, we create a new data source for Raft autopilot state.Output from acceptance testing: