Skip to content
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

CLI Utility to execute common CI/CD tasks #183

Open
rweintraub-cycleon opened this issue Mar 29, 2023 · 1 comment
Open

CLI Utility to execute common CI/CD tasks #183

rweintraub-cycleon opened this issue Mar 29, 2023 · 1 comment

Comments

@rweintraub-cycleon
Copy link

Hi,

this project looks quite promising but while i was trying to set up the registry locally & thinking about how to approach a CI/CD scenario it felt there was a small CLI utility missing.

Ideally i think such a small CLI could help with these topics:

  • pipelines/stacks that are not do not use node as of now will be able interact with the registry easily
  • easily push a new schema during a deploy task by pushing the schema.graphql
  • easily validate if the pipeline is safe to deploy a new version

i hope the request makes sense. I could also support in building such a CLI utility

@tot-ra
Copy link
Owner

tot-ra commented May 9, 2023

hey. Yes, thats somewhat useful if your service has a static schema and you need it only in for some CI tasks. For example it would be nice in github PR to display inline comments where schema is invalid. Perhaps https://the-guild.dev/graphql/inspector could be integrated?

In production however, you may find that it's the service that needs to register the schema and handle failure. The schema can be also generated in runtime out of some typescript code.

For the regular code, you can look into some examples (and add more - related #151 )
https://github.com/tot-ra/graphql-schema-registry/tree/master/examples/schema_registration_client

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants