scripts: Omit canned ACL from uploads to container buckets

The public-read canned ACL is redundant as the buckets are configured to
be publicly readable at the bucket level. Thus, we can drop the ACL from
individual objects, allowing the buckets to be set to the recommended
"Uniform" access control model which does not allow object ACLs.

BUG=none
TEST=none

Change-Id: Iea00fc597bc225749d474f96d2c120aef4135edb
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/3398059
Reviewed-by: David Munro <davidmunro@google.com>
Reviewed-by: Fergus Dall <sidereal@google.com>
Auto-Submit: James Ye <jamesye@google.com>
Tested-by: kokoro <noreply+kokoro@google.com>
Commit-Queue: James Ye <jamesye@google.com>
2 files changed
tree: 78b2e86000eec837ad263377815cf5bca0a7642f
  1. cros-adapta/
  2. cros-apt-config/
  3. cros-debs/
  4. cros-garcon/
  5. cros-gpu-buster/
  6. cros-guest-tools/
  7. cros-host-fonts/
  8. cros-logging/
  9. cros-notificationd/
  10. cros-pulse-config/
  11. cros-sftp/
  12. cros-sommelier/
  13. cros-sommelier-config/
  14. cros-sudo-config/
  15. cros-systemd-overrides/
  16. cros-tast-tests/
  17. cros-ui-config/
  18. cros-wayland/
  19. docs/
  20. kokoro/
  21. lxd/
  22. mesa/
  23. scripts/
  24. termina/
  25. .gitignore
  26. LICENSE
  27. OWNERS
  28. PRESUBMIT.cfg
  29. README.md
  30. WORKSPACE
README.md

cros-container-guest-tools

Overview

These are the guest packages for setting up a container to integrate with Chrome OS. This includes build scripts that are run in Google's internal continuous integration service.

Building

The guest packages can be built with Bazel.

bazel build //cros-debs:debs

Releasing

promote\_apt.sh MILESTONE and promote\_container.sh MILESTONE in scripts are used to promote containers from staging to live. NOTE: Whatever is the latest in staging is what gets promoted to live so make sure it's what was tested.