…1110)"

This reverts commit 28cf6a9.

Description

Unfortunately gcloud has a (unknown to me) built-in security check, which enforces that if a service account binding with a condition exists, then other bindings without condition can no longer be created unless --condition=None is specified. This is a problem for us because it breaks the existing code on release branches. So before introducing such a condition, we first need to bulletproof the existing code on release branches to make it forward compatible.

Example error:

(gcloud.iam.service-accounts.add-iam-policy-binding) Adding a binding without specifying a condition to a policy containing conditions is prohibited in non-interactive mode. Run the command again with `--condition=None`

Note: This PR has two commits. The first is the revert, the second is adding --condition=None to make sure CI passes.

User-facing documentation

• CHANGELOG.md is updated OR update is not needed
• documentation PR is created and is linked above OR is not needed

Testing and quality

• the change is production ready: the change is GA, or otherwise the functionality is gated by a feature flag
• CI results are inspected

Automated testing

• added unit tests
• added e2e tests
• added regression tests
• added compatibility tests
• modified existing tests

How I validated my change

change me!