-
Notifications
You must be signed in to change notification settings - Fork 30
Integrate bm #146
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
base: master
Are you sure you want to change the base?
Integrate bm #146
Conversation
…ider-azurestackhci
Merge to ecf baseline
Location value is being provided instead of a group value.
* Use new moc package's providerid functions. Use the new `providerid.FormatProviderID` function in MOC package instead of manually formatting the provider ID. This also inherently adds support for bare-metal provider IDs. * go.mod updates
…rkaround Remove load balancer workaround for bare metal.
…mCleanup Pre-upstream cleanup
Should we drop BM changes out of v1alpha3? |
Not sure I understand the proposal here? |
Since at the time of upstreaming v1alpha4 is already present, should we include the BM changes into the v1alpha3 API of CAPH or just into v1alpha4. |
I would vote for v1apha4 unless there will be significant cost associated. |
Depends on microsoft/moc-sdk-for-go#68 and microsoft/moc#84. Dependencies will need to be updated once the lower layer PRs are merged.