-
Notifications
You must be signed in to change notification settings - Fork 87
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
Redesign plane resource types #7499
Conversation
docs/contributing/contributing-code/contributing-code-control-plane/configSettings.md
Show resolved
Hide resolved
pkg/ucp/backend/controller/resourcegroups/trackedresourceprocess_test.go
Show resolved
Hide resolved
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #7499 +/- ##
==========================================
+ Coverage 60.25% 60.31% +0.06%
==========================================
Files 507 517 +10
Lines 26265 26432 +167
==========================================
+ Hits 15825 15943 +118
- Misses 9105 9140 +35
- Partials 1335 1349 +14 ☔ View full report in Codecov by Sentry. |
pkg/ucp/integrationtests/planes/testdata/awsplane_updated_v20231001preview_requestbody.json
Show resolved
Hide resolved
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
6d98b60
to
ce2bf68
Compare
@youngbupark @ytimocin can you take a look when you have a chance? I need to figure out my one failing test, but that is likely a swagger update I missed. |
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.
Since this is a huge update, it is not easy to review the entire code thoroughly. Overall looks good to me. I will have some time to review this PR in detail tomorrow. meanwhile, please fix the test :)
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
...ecification/ucp/resource-manager/UCP/preview/2023-10-01-preview/examples/AwsPlanes_List.json
Show resolved
Hide resolved
...esource-manager/UCP/preview/2023-10-01-preview/examples/AzureCredentials_CreateOrUpdate.json
Show resolved
Hide resolved
...tion/ucp/resource-manager/UCP/preview/2023-10-01-preview/examples/AzureCredentials_List.json
Show resolved
Hide resolved
@ytimocin - updated |
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
pkg/ucp/integrationtests/planes/testdata/awsplane_v20231001preview_list_responsebody.json
Show resolved
Hide resolved
This change splits the plane resource type into multiple types for maintainability as reviewed in radius-project/design-notes#42. See the design document for the motivation and dicussion of the specific design details. In summary, previously we had one resource type for all planes, and now we have a few separate ones. This is a technically a breaking change but the impact on users is very low because it's mainly UCP itself that interacts with the planes. The majority of the code changes are due to: Simplifying the resource group client API Updating and adding examples Signed-off-by: Ryan Nowak <nowakra@gmail.com>
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Thanks @ytimocin ! |
Description
This change splits the plane resource type into multiple types for maintainability as reviewed in radius-project/design-notes#42. See the design document for the motivation and dicussion of the specific design details. In summary, previously we had one resource type for all planes, and now we have a few separate ones.
This is a technically a breaking change but the impact on users is very low because it's mainly UCP itself that interacts with the planes.
The majority of the code changes are due to:
Type of change
Fixes: #issue_number