Google APIs 0a992df802 feat: add canonical_name and folder fields ... Assets and findings may be created in organizations, folders or projects, however in the current API version the name field for resources will always be prefixed by "organizations/...", for historical reasons. The "canonical_name" field shows the actual location of the resource, and in requests either the name or "canonical name" can be used for the "name" in the request. The "folder" field contains the folders in the resource's ancestry. PiperOrigin-RevId: 372965035		2021-05-10 11:04:03 -07:00
..
asset.proto	feat: add canonical_name and folder fields	2021-05-10 11:04:03 -07:00
BUILD.bazel	feat: add canonical_name and folder fields	2021-05-10 11:04:03 -07:00
finding.proto	feat: add canonical_name and folder fields	2021-05-10 11:04:03 -07:00
folder.proto	feat: add canonical_name and folder fields	2021-05-10 11:04:03 -07:00
notification_config.proto	feat: add canonical_name and folder fields	2021-05-10 11:04:03 -07:00
notification_message.proto	feat: add canonical_name and folder fields	2021-05-10 11:04:03 -07:00
organization_settings.proto	feat: add canonical_name and folder fields	2021-05-10 11:04:03 -07:00
resource.proto	feat: add canonical_name and folder fields	2021-05-10 11:04:03 -07:00
run_asset_discovery_response.proto	feat: add canonical_name and folder fields	2021-05-10 11:04:03 -07:00
security_marks.proto	feat: add canonical_name and folder fields	2021-05-10 11:04:03 -07:00
securitycenter_grpc_service_config.json	fix: correct securitycenter grpc_service_configs	2020-07-13 11:22:33 -07:00
securitycenter_service.proto	feat: add canonical_name and folder fields	2021-05-10 11:04:03 -07:00
securitycenter_v1.yaml	feat: add canonical_name and folder fields	2021-05-10 11:04:03 -07:00
source.proto	feat: add canonical_name and folder fields	2021-05-10 11:04:03 -07:00