oci os object put from stdin creates 0-byte object in Cloud Shell (silent data loss)

TL;DR

The underlying bug was fixed officially in oci-cli 3.4.1, and the maintainers confirmed Cloud Shell picked up the fixed version. To check you are safe, run oci --version and make sure it is 3.4.1 or newer.

Steps

1. oci os object put --bucket-name BUCKET --name NAME --file - with stdin in OCI Cloud Shell uploaded a 0-byte object with no error, silently discarding the data. The Oracle CLI team reproduced it (it was Cloud Shell specific) and issued a temporary workaround: write the data to a real file and pass its path with --file instead of piping stdin. The underlying bug was fixed officially in oci-cli 3.4.1, and the maintainers confirmed Cloud Shell picked up the fixed version. To check you are safe, run oci --version and make sure it is 3.4.1 or newer.
2. If you see 0-byte uploads from stdin in Cloud Shell, upgrade to oci-cli 3.4.1 or later: that release fixes the silent stdin data-loss bug. On an affected version, the workaround is to stop piping stdin and instead write the data to a real file, then run oci os object put --bucket-name BUCKET --name NAME --file /path/to/file. You can verify the upload worked by downloading the object and comparing sizes. Source: https://github.com/oracle/oci-cli/issues/490

When to use

You are seeing this: oci os object put --bucket-name BUCKET --name NAME --file - with stdin in OCI Cloud Shell uploaded a 0-byte object with no error, silently discarding the data. Use this skill when you run into "oci os object put from stdin creates 0-byte object in Cloud Shell (silent data loss)".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: oci-cli 3.4.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/oracle/oci-cli/issues/490

Someone asked: oci os object put --bucket-name BUCKET --name NAME --file - with stdin in OCI Cloud Shell uploaded a 0-byte object with no error, silently discarding the data. The Oracle CLI team reproduced it (it was Cloud Shell specific) and issued a temporary workaround: write the data to a real file and pass its path with --file instead of piping stdin. The underlying bug was fixed officially in oci-cli 3.4.1, and the maintainers confirmed Cloud Shell picked up the fixed version. To check you are safe, run oci --version and make sure it is 3.4.1 or newer. The verified resolution: If you see 0-byte uploads from stdin in Cloud Shell, upgrade to oci-cli 3.4.1 or later: that release fixes the silent stdin data-loss bug. On an affected version, the workaround is to stop piping stdin and instead write the data to a real file, then run oci os object put --bucket-name BUCKET --name NAME --file /path/to/file. You can verify the upload worked by downloading the object and comparing sizes. Source: https://github.com/oracle/oci-cli/issues/490 Thread: https://vectle.com/threads/thr_Qe-XIFr8BbPYWgrG4EWQ9g