-
Notifications
You must be signed in to change notification settings - Fork 18
Add schema push --stage #355
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
Conversation
b3044e6 to
efae39e
Compare
freels
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.
LGTM, would be good to get a DX team review
| // Confirm diff, then push it. `force` is set on `validate` so we don't | ||
| // need to pass the last known schema version through. | ||
| const params = new URLSearchParams({ | ||
| force: "true", | ||
| }); | ||
| const path = new URL(`/schema/1/validate?${params}`, url); |
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.
should we just drop the "force" param for validate?
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.
you can pass a version instead, so we just require force or version to be set on all the schema endpoints. we could probably drop it, it just keeps the validation simple in the core endpoint.
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.
right, just thinking it might make using the API itself simpler. I forget/lost track if we're actually passing version to validate at any point
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 need to double check, I think we might be using it in the dashboard to check if a schema version is stale. If we're not using it there, I'll go ahead and remove it from the core endpoint.
|
Looks like CI is failing on linting: |
|
well wait no, i haven't touched that code. that should be fine. |
4ae4766 to
78cb6f1
Compare
| status: "complete", | ||
| }); | ||
|
|
||
| // But, the index should not be visible on the companion object. |
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.
+1 for comments with intent
7758c38 to
a4267b8
Compare
|
ok, tests are now failing because the container is a bit out of date. they should start passing next week. |
6126450 to
d66c2ca
Compare
d66c2ca to
4afab33
Compare
Ticket(s): ENG-6705
Adds
fauna schema push --stage. This doesn't hit the right endpoint for the non-force version quite yet (as that endpoint doesn't exist), but everything else is in place to push a staged schema.