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

Packager docs #4303

Draft
wants to merge 18 commits into
base: master
Choose a base branch
from
Draft

Packager docs #4303

wants to merge 18 commits into from

Conversation

drernie
Copy link
Member

@drernie drernie commented Jan 29, 2025

Description

Proposed documentation (in-process) for the Quilt Packager, to help us align on terminology and features.

TODO

  • Documentation
    • run optipng on any new PNGs
    • Markdown somewhere in docs/**/*.md that explains the feature to end users (said .md files should be linked from SUMMARY.md so they appear on https://docs.quiltdata.com)
    • Markdown docs for developers
  • Changelog entry (skip if change is not significant to end users, e.g. docs only)

@drernie drernie marked this pull request as draft January 29, 2025 02:33
@drernie drernie requested a review from QuiltSimon January 29, 2025 02:33
Copy link

codecov bot commented Jan 29, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 39.11%. Comparing base (bb32796) to head (804f470).

Additional details and impacted files
@@           Coverage Diff            @@
##           master    #4303    +/-   ##
========================================
  Coverage   39.11%   39.11%            
========================================
  Files         783      783            
  Lines       34737    34737            
  Branches     5308     5517   +209     
========================================
  Hits        13586    13586            
+ Misses      20608    19970   -638     
- Partials      543     1181   +638     
Flag Coverage Δ
api-python 91.39% <ø> (ø)
catalog 18.12% <ø> (ø)
lambda 91.48% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary

This PR introduces comprehensive documentation for the Quilt Packaging Service (QPS), detailing automated package creation from S3 data through various integration methods.

  • Documentation needs clarification on SNS notification behavior (marked as TBD)
  • Fix broken link to [nf-prov(nf-prov)] in /docs/Catalog/Packager.md
  • Correct typo "foldler" to "folder" in /docs/Catalog/Packager.md
  • Add missing response format documentation for REST API endpoints in /docs/Catalog/Packager.md
  • Consider running optipng on packager-admin-gui.png as per TODO list

2 file(s) reviewed, 4 comment(s)
Edit PR Review Bot Settings | Greptile

docs/Catalog/Packager.md Outdated Show resolved Hide resolved
docs/Catalog/Packager.md Outdated Show resolved Hide resolved
docs/Catalog/Packager.md Outdated Show resolved Hide resolved
Comment on lines 14 to +15
* [Embeddable iFrames](Catalog/Embed.md)
* [Packaging Service](Catalog/Packager.md)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

style: Consider renaming to 'Quilt Packaging Service (QPS)' to match the title used in Packager.md for consistency

create packages. Any event that matches one of these rules will be sent to the
`QuiltPackager` SQS queue.

1. The `detail-type` is `package-objects-request`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe package-objects-ready?
BTW we also have package-objects-ready-glob

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have a single endpoint for both? Then yeah, that makes sense.
What does 'package-objects-ready-glob' mean? Does it have different arguments?
Should we sending 's3://bucket/folder/*'?

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

Successfully merging this pull request may close these issues.

2 participants