-
Notifications
You must be signed in to change notification settings - Fork 351
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: cli warp route checker #4667
base: main
Are you sure you want to change the base?
Conversation
…rmat the logged command header
…n to get the warp route config from the registry or file based on the user input
…d defined the DEFAULT_WARP_ROUTE_DEPLOYMENT_CONFIG_PATH const
…arp check command
🦋 Changeset detectedLatest commit: aef7fd7 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 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4667 +/- ##
=======================================
Coverage 73.85% 73.85%
=======================================
Files 100 100
Lines 1423 1423
Branches 181 181
=======================================
Hits 1051 1051
Misses 351 351
Partials 21 21
|
…onfig files with on chain warp route deployments
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.
quite cool
a little wary of the SDK schema changes
…to xeno/cli-warp-route-checker
Description
This PR implements the
warp check
command to compare on-chain warp deployments with provided configuration filesDrive-by changes
inputFileCommandOption
to be a function for defining cli input file argsDEFAULT_WARP_ROUTE_DEPLOYMENT_CONFIG_PATH
to avoid hardcoding the./configs/warp-route-deployment.yaml
file pathlogCommandHeader
function to format the command header and avoid always having to manually log the---
separator in command outputsgetWarpCoreConfigOrExit
to get the warp core configuration from either the registry or a user-defined path and exit early if no input value is providedIsmConfigSchema
s to include theBaseIsmConfigSchema
because when parsing config files the address field was not included in the parsed object as it wasn't defined on the typeExample output
Related issues
Backward compatibility
Testing