Attachments

Attachments

English · 繁體中文

taiga attachment list issue 42
taiga attachment add issue 42 ./error.log --description "Build failure"
cat error.log | taiga attachment add issue 42 - --name error.log
taiga attachment view issue 17
taiga attachment download issue 17 --output ./error.log
taiga attachment edit issue 17 --description "Resolved" --deprecated
taiga attachment delete issue 17 --yes

taiga attachment add epic 8 ./proposal.pdf
taiga attachment add wiki api-guide ./diagram.png

Supported resources

issue, story, task, epic, and wiki. Wiki pages are addressed by slug; everything else by ref.

Uploads

Uploads stream as multipart and never read the whole file into memory. To upload from stdin, pass - as the path and give the filename with --name.

Download integrity

attachment download makes several deliberate choices:

• The API bearer token is never sent to the media URL. Attachment bytes are usually served by object storage or a reverse proxy, where an API credential is both unnecessary and risky.
• SHA-1 and SHA-256 are computed while downloading and checked against the digest and size Taiga recorded; a mismatch is an error.
• The data is written to a 0600 temporary file first and only replaces the destination atomically once it verifies.
• An existing file is not overwritten by default.

Deleting requires --yes when non-interactive.