We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Migrate from graphql-slack-updater to a weekly peril job.
None, as each GraphQL server would need to be added individually. So start with metaphysics, and wait depending on how far stitching is along.
Will be the first time that Peril uploads something to S3, so will need to add support for that..
For devs: GitHub event ID: ac11df00-0366-11e8-991a-ee17164aa737
GitHub event ID: ac11df00-0366-11e8-991a-ee17164aa737
The text was updated successfully, but these errors were encountered:
👍 from me assuming the setup / takedown process is well-documented.
Sorry, something went wrong.
It'd probably end up as a single file of JS, so should be pretty easy to grok. The CLI version was under 100 LOC, so shouldn't be too bad I expect.
This is in with #84
No branches or pull requests
Proposal:
Migrate from graphql-slack-updater to a weekly peril job.
Reasoning
Exceptions:
None, as each GraphQL server would need to be added individually. So start with metaphysics, and wait depending on how far stitching is along.
Additional Context:
Will be the first time that Peril uploads something to S3, so will need to add support for that..
For devs:
GitHub event ID: ac11df00-0366-11e8-991a-ee17164aa737
The text was updated successfully, but these errors were encountered: