Comment 5 for bug 1204558

The first error has turned into a warning, as Janie pointed out. Even before https://github.com/openstack/python-swiftclient/commit/9593d4b, though, an upload via a write-only ACL would be possible; it'd just require --leave-segments (since you cannot read the object to determine whether it's some flavor of large object) and it would exit non-zero.

We might further improve things by:

- adding an option to skip the container PUT, so we don't even display the warning about being unable to create the container and
- documenting how write-only access requires the use of --leave-segments (since you cannot read the object to determine whether it's some flavor of large object)

I proposed https://review.opendev.org/c/openstack/python-swiftclient/+/824281 to add a --skip-container-put option at least.