Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-4109

Support arbitrary artifact names in local file artifact staging service

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: runner-core
    • Labels:
      None

      Description

      The local-file based artifact staging service implementation stores artifacts in a flat directory under the exact names they are given by the artifact staging request. This assumes that all artifact names are safe file names and requires staging clients to manually escape names.

      Instead, the staging service should perform its own escaping/mapping transparently and allow clients to specify arbitrary artifact staging names.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                bsidhom Ben Sidhom
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: