--- title: "2026-08-28 VxData multipart upload software maps" description: "Authored commit-pinned base and head software maps for the VxData multipart upload Review." image: "https://docs.virdx.dev/img/virdx-social-card.png" --- > Documentation Index > Fetch the complete documentation index at: https://docs.virdx.dev/llms.txt > Use this file to discover all available pages before exploring further. # 2026-08-28 VxData multipart upload software maps ## Work Done - Authored the base software map for commit `d2ab806ccdc33997124ba50c1d30cf2c0e0362db`. - Modeled the VxData Python SDK storage namespace, transfer engine, HTTP transport, direct-S3 adapter, shared storage schemas, API routes and service, S3 object store, and caller filesystem. - Updated that structure for head commit `350b1823f0b1a8092130846074f3993963bf4fe1` to show multipart upload planning, streaming, ETag checks, upload-key validation, and create/presign/complete/abort lifecycle operations. - Both `review map check` commands passed and saved git notes under `refs/notes/dev-fast/software-map`. The Review document and published map state were not changed. ## Lessons Learned: Pitfalls - `review map open ` did not seed from the checked base note because the base commit is the second parent of a merge rather than a first-parent ancestor. Reopening with `--force` still produced a schema stub, so the checked base map had to be copied into the head scratch file manually before applying the diff. - Relationship endpoints use normalized element paths such as `vxdataPlatform.pythonSdk.storageNamespace`; collection names such as `systems`, `containers`, and `components` are not part of those paths. - A broad `**/*.py` parent coverage glob did not satisfy coverage validation for direct child files in this map. Explicit parent file coverage worked. ## Lessons Learned: Improvements - Add normalized relationship-path examples to the software-map authoring instructions. - Document that a Review base can be a merge commit's second parent, while head seeding only follows first parents, and describe the manual base-map copy fallback. - Add a short coverage-glob reference or validator example to clarify supported glob behavior. Source: https://docs.virdx.dev/knowledge/inbox/2026-08-28-infrastructure-vxdata-multipart-software-maps/index.mdx