daylily-omics-references
Bash utilities for creating and validating the reference S3 buckets used by
daylily-ephemeral-cluster.
The project now ships a single shell script that wraps AWS CLI commands to clone
public reference data, validate an existing bucket, or ensure a bucket exists
and matches the expected structure.
The commands shell out to the AWS CLI for recursive S3 copy operations. Ensure that the AWS CLI and
jqare installed and that your environment is authenticated before running the script.
Usage
The entry point lives at scripts/daylily-omics-references.sh. Global options
may be placed before the subcommand.
Usage: daylily-omics-references.sh [GLOBAL OPTIONS] <command> [ARGS]
Global options:
--profile PROFILE AWS profile to use
--region REGION AWS region to target (required for clone/ensure)
Commands:
clone Create a new reference bucket from the public source
verify Validate that a bucket matches the expected structure
ensure Verify a bucket or create it if missing
Clone a new reference bucket
scripts/daylily-omics-references.sh \
--profile daylily-service \
clone \
--bucket-prefix myorg \
--region us-west-2 \
--execute
This creates myorg-omics-analysis-us-west-2, enables transfer acceleration
and copies the default reference version (0.7.131c). Use --exclude-hg38,
--exclude-b37, or --exclude-giab to omit large subsets. Pass
--use-acceleration to copy via the S3 accelerate endpoint.
Verify an existing bucket
scripts/daylily-omics-references.sh \
--profile daylily-service \
verify \
--bucket myorg-omics-analysis-us-west-2
This validates that the bucket exists, contains the expected folder structure
and that its s3_reference_data_version.info marker matches the default
version.
Ensure a bucket is ready for daylily-ephemeral-cluster
scripts/daylily-omics-references.sh \
--profile daylily-service \
ensure \
--bucket-prefix myorg \
--region us-west-2 \
--execute
The command verifies the bucket when it already exists; otherwise it creates the bucket using the same cloning logic.
Development
The repository now consists solely of the bash script above. No Python dependencies are required. If you modify the script, ensure it remains POSIX shell compatible and keep the usage examples up to date.
Metadata
Release files for daylily-omics-references 0.3.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| daylily_omics_references-0.3.3.tar.gz | 21.1 kB | Without provenance | Details for daylily_omics_references-0.3.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| daylily_omics_references-0.3.3-py3-none-any.whl | Python 3 | none | any | Details for daylily_omics_references-0.3.3-py3-none-any.whl |
Total release size: 42.3 kB
Release files / daylily_omics_references-0.3.3.tar.gz
| Download URL | daylily_omics_references-0.3.3.tar.gz |
|---|---|
| Size | 21.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2a3ef41678940780729c3ffd080bd7116ee20f63012d4b1d7ec8d780f6786ec3
|
|
BLAKE2b-256 checksum How to use checksums |
eec13a2932acf5d9b1d711c0e60fea54151204dd8b577fd492c5d12e8c3caccb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / daylily_omics_references-0.3.3-py3-none-any.whl
| Download URL | daylily_omics_references-0.3.3-py3-none-any.whl |
|---|---|
| Size | 21.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2092e39330450ec9a137265b5c301e91259dcdb9de8aeebd4dd7dac88c8d522f
|
|
BLAKE2b-256 checksum How to use checksums |
af53f0aaf17c54543bbdbe465fccf8381704d1823c818cdfb0f1338f2a9757a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for daylily-omics-references 0.3.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.