An update to Go gRPC Protobuf generation will change service registration function signatures to use an interface instead of a concrete type in generated .pb.go service files. This change should affect very few client library users. See release notes advisories in https://github.com/googleapis/google-cloud-go/pull/11025.
PiperOrigin-RevId: 766242721
feat: A new value `REMOVE_GRANT` is added to enum `MethodType`
feat: A new value `GOVERN_TAGS` is added to enum `MethodType`
feat: A new message `AssetEnrichment` is added
feat: A new field `enrichments` is added to message `.google.cloud.asset.v1.ResourceSearchResult`
docs: A comment for field `service_account_impersonation_analysis` in message `.google.cloud.asset.v1.AnalyzeIamPolicyResponse` is changed
docs: A comment for field `consolidated_policy` in message `.google.cloud.asset.v1.AnalyzeOrgPoliciesResponse` is changed
docs: A comment for field `policy_bundle` in message `.google.cloud.asset.v1.AnalyzeOrgPoliciesResponse` is changed
docs: A comment for field `policy_bundle` in message `.google.cloud.asset.v1.AnalyzeOrgPolicyGovernedContainersResponse` is changed
docs: A comment for field `policy_bundle` in message `.google.cloud.asset.v1.AnalyzeOrgPolicyGovernedAssetsResponse` is changed
docs: A comment for field `attached_resource` in message `.google.cloud.asset.v1.EffectiveTagDetails` is changed
PiperOrigin-RevId: 750916403
chore(python): Add build for //google/identity/accesscontextmanager/v1:accesscontextmanager_py_proto to prepare for release
chore(python): Comment out build for //google/identity/accesscontextmanager/v1:accesscontextmanager_py_gapic which is currently not used
PiperOrigin-RevId: 710069242
feat: Add `effective_tags` field to `GovernedResource`
feat: Add fields `project`, `folders`, `organization` and `effective_tags` to `GovernedContainer`
feat: Add fields `project`, `folders` and `organization` to `OrgPolicyResult`
feat: Add field `condition_evaluation` to `AnalyzerOrgPolicy.Rule`
docs: Update comment for rpc `AnalyzeOrgPolicyGovernedAssets` to include additional canned constraints
PiperOrigin-RevId: 612934037
docs: clarify comments for tags and effective tags
Clients can search resources filtered by effective tags and start to use the new `tags` field instead of old `tag_key`, `tag_value`, `tag_value_id` fields to access directly attached tags.
PiperOrigin-RevId: 567554529
