#3410 Use signedURL endpoint override for signed URLs generated by flyte in sandbox-bundled Pull request opened by jeevb Added a raw container test in sandbox-bundled, and tested with that for now. Ideally we run a full suite of tests against this sandbox, but we can add that later. Init container args for raw container tasks are correct now:

flyte-copilot-downloader:
    Container ID:  <containerd://8d644476e1479f9c3eb5b700d56c8a1b18b1a2aac10d80e7d1f8da0c4758401a>
    Image:         <http://cr.flyte.org/flyteorg/flytecopilot:v0.0.15|cr.flyte.org/flyteorg/flytecopilot:v0.0.15>
    Image ID:      <http://cr.flyte.org/flyteorg/flytecopilot@sha256:d6e4efb8509caf178c04df9842e4a321657327e72381f304550b5b8401dd8c25|cr.flyte.org/flyteorg/flytecopilot@sha256:d6e4efb8509caf178c04df9842e4a321657327e72381f304550b5b8401dd8c25>
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/flyte-copilot
      --storage.limits.maxDownloadMBs=0
      --storage.container=my-s3-bucket
      --storage.type=stow
      --storage.stow.config
      v2_signing=1
      --storage.stow.config
      endpoint=<http://flyte-sandbox-minio.flyte:9000>
      --storage.stow.config
      auth_type=accesskey
      --storage.stow.config
      access_key_id=minio
      --storage.stow.config
      secret_key=miniostorage
      --storage.stow.config
      region=us-east-1
      --storage.stow.config
      disable_ssl=1
      --storage.stow.kind=s3
    Args:
      download
      --from-remote
      <s3://my-s3-bucket/metadata/propeller/flytesnacks-development-f7a176b1a662f4053be6/n0/data/inputs.pb>
      --to-output-prefix
      <s3://my-s3-bucket/metadata/propeller/flytesnacks-development-f7a176b1a662f4053be6/n0/data/0>
      --to-local-dir
      /var/flyte/inputs
      --format
      JSON
      --input-interface
      Cg8KB2NvbW1hbmQSBAoCCAM=

flyteorg/flyte ✅ All checks have passed 12/12 successful checks