-
Notifications
You must be signed in to change notification settings - Fork 446
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
refactor: optional mailbox on warp config #5500
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 1c322ec The changes in this PR will be included in the next version bump. This PR includes changesets to release 9 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
typescript/infra/config/warp.ts
Outdated
@@ -125,6 +125,8 @@ async function getConfigFromMergedRegistry( | |||
true, | |||
).getWarpDeployConfig(warpRouteId); | |||
assert(warpRoute, `Warp route Config not found for ${warpRouteId}`); | |||
//TODO: fix this and manage mailbox |
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.
@nambrot Can you please take a look at this?
should I handle mailbox on infra side or on registry itself?
So I need to do similar thing fillDefaults
did on cli.
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.
As mailbox may not return when we call getWarpDeployConfig
from registry
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 think the Registry should handle this, given that the mailbox address comes from the Registry
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.
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.
on second thought, i am kind of leaning towards keeping that Registry function as is i.e. to fetch the non-derived.
do the callers actually need the mailbox here?
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.
This is a great question, I'm inclined to change the return type here and then see where it breaks. Generally speaking would prefer to pass around the "simpler" version and then only "hydrate" the config when necessary
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 believe this would be needed on deploy script of infra, so we really needed and should decide for the way we get it.
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.
yeah lets keep the Registry as is and then do some sort of filldefault() here
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.
got it, done!
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5500 +/- ##
=======================================
Coverage 77.53% 77.53%
=======================================
Files 103 103
Lines 2110 2110
Branches 190 190
=======================================
Hits 1636 1636
Misses 453 453
Partials 21 21
🚀 New features to boost your workflow:
|
…ve ts-ignore workaround
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.
Would like explicit approval from @ltyu as well but lgtm
Description
This PR updates the warp route deployment configuration to handle mailbox addresses more consistently. Key changes:
Drive-by changes
Related issues
#5258
Backward compatibility
Yes - This change maintains backward compatibility while improving the internal handling of mailbox addresses.
Testing
Unit Tests - Existing tests have been updated to accommodate the new mailbox handling approach