-
Notifications
You must be signed in to change notification settings - Fork 2
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
Switch to schema-push model (rather than schema-pull) #195
Comments
@jalyna thoughts? These are some reflections from explaining to @psteininger how the current system works |
@nickcampbell18 This is a really nice suggestion. This was the very first approach, when we only had one 2 Apps. So I think we should invest some time to improve this. |
Do you have a preference for GitHub action vs CircleCI orb? I can probably bring across some of the code I wrote before to do this... |
No preference whatsoever. I think that whichever looks less complex to comprehend. |
I would believe that github actions might be easier here but just an assumption. |
Currently, the docs site pulls schema from different URLs at build time. This has a few consequences:
I propose we switch to a schema-push model. I've used this successfully in the past - it's a more explicit workflow that allows better auditing of behaviour. It looks like this:
Benefits of this approach:
Downsides:
The text was updated successfully, but these errors were encountered: