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
feat: write a wrapper for the provisioner to call gw and r-r clients #1585
feat: write a wrapper for the provisioner to call gw and r-r clients #1585
Conversation
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.
Looks correct to me so far, thanks Pieter!
…-a-wrapper-for-the-provisioner-to-call-gwr-r-clients
Having this trait in `limits.rs` exposes too much to c-s and user services.
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.
I left a question about observability, and I'm also curious to know why those tests are failing in CI. Otherwise, this lgtm!
…-a-wrapper-for-the-provisioner-to-call-gwr-r-clients
The tests kept failing on the CI for what appears to be the tokio spawn of the server shutting down since it gave errors for the client not being able to connect.
I needed to move the internal `tracing` module to `trace` to prevent a clash with the `tracing` library.
c4efc96
to
8989dfa
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.
Thanks, one small question, but LGTM 🥳
Description of change
Allows provisioner to check how many RDSs a user is already using before trying to provision a new one.
How has this been tested? (if applicable)
A whole lot of new tests