-
-
Notifications
You must be signed in to change notification settings - Fork 12
Upstream changes from Aspen Cloud #19
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
base: main
Are you sure you want to change the base?
Conversation
Update package.json
sweatybridge
left a comment
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.
Apart from regenerating types and new gql client methods, this PR adds the following functionality
- supports
fly-machine-lease-nonceheader in updateMachine - supports
deleteLeaseoperation
Did I miss anything?
| async getAppDetailed( | ||
| app_name: GetAppRequest | ||
| ): Promise<APIResponse<AppDetailedResponse>> { | ||
| const response = await this.client.safeGqlPost<string, { app: any }>({ |
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.
Can we avoid typing app: any in calls to safeGqlPost? Always define the interface types returned from graphql api call.
| async listMachines(app_name: ListMachineRequest): Promise<MachineResponse[]> { | ||
| async listMachines( | ||
| app_name: ListMachineRequest | ||
| ): Promise<APIResponse<MachineResponse[]>> { |
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.
What's the reason for wrapping errors in the response object instead of throwing? This would be a breaking change for existing users of this library which I'd like to avoid.
A few other options
- create another wrapper class
- bump the major version
Co-authored-by: Han Qiao <[email protected]>
Co-authored-by: Han Qiao <[email protected]>
Overview
This brings in some of the changes we used at Aspen Cloud to run Triplit Cloud. We used these changes (in our own fork) in production to deploy, update, and manage applications and machines on Fly.
Changes