-
Notifications
You must be signed in to change notification settings - Fork 97
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
Add dynamic-rp boilerplate #8029
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #8029 +/- ##
==========================================
- Coverage 59.35% 59.08% -0.27%
==========================================
Files 561 567 +6
Lines 37551 37728 +177
==========================================
+ Hits 22287 22293 +6
- Misses 13714 13887 +173
+ Partials 1550 1548 -2 ☔ View full report in Codecov by Sentry. |
39392e7
to
76773f5
Compare
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... |
76773f5
to
b6cb602
Compare
Note: I'm still digging into the functional test failure. I don't have a theory yet on how this change could have broken those 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... |
This change adds a new control-plane microservice - the "Dynamic RP". The dynamic-rp will be responsible for implementing the bulk of UDT functionality. The naming reflects that fact that dynamic-rp behaves *dynamically* based on the schema definitions provided by users. This change only contains the *base layer* for dynamic-rp and no user-visible functionality. Here's a brief list of what's included. - dynamic-rp binary - dynamic-rp Dockerfiles - dynamic-rp Kubernetes yaml - dynamic-rp configuration file - initialization and stubs for frontend and backend services - vscode debugging support - functional test integration The actual functionality for dynamic-rp will be added in a series of follow-up pull-requests. Signed-off-by: Ryan Nowak <[email protected]>
b6cb602
to
e8eb235
Compare
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... |
This turned out to be interesting. I accidentally configured both dynamic-rp and applications-rp to read from the same queue. The logs pointed me at the problem 😆 because dynamic-rp tried to process a change it didn't understand. |
Still fighting with the functional tests here, will report back. |
Looks like this will need a bypass. The problem is that I need to make changes to the functional test workflow to set the new image location/tag. I'll force merge this and then babysit the build. |
Description
This change adds a new control-plane microservice - the "Dynamic RP". The dynamic-rp will be responsible for implementing the bulk of UDT functionality. The naming reflects that fact that dynamic-rp behaves dynamically based on the schema definitions provided by users.
This change only contains the base layer for dynamic-rp and no user-visible functionality. Here's a brief list of what's included.
The actual functionality for dynamic-rp will be added in a series of follow-up pull-requests.
Please explain the changes you've made.
Type of change
Part of: #6688
Contributor checklist
Please verify that the PR meets the following requirements, where applicable: