Represents the metadata for a Google Cloud Storage HmacKeyResource.
HMAC keys allow applications to authenticate with Google Cloud Storage using HMAC authentication. Applications can create a limited number of HMAC keys associated with a service account. The application can use the HMAC keys to authenticate with GCS. GCS will use the service account permissions to determine if the request is authorized.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["This document outlines the `HmacKeyMetadata` class, which is used to manage metadata for Google Cloud Storage HMAC keys, enabling applications to authenticate with GCS."],["The content provides a comprehensive list of versions for the `HmacKeyMetadata` class, starting from version 2.11.0 up to the latest release candidate 2.37.0-rc, allowing developers to find relevant documentation for their specific version."],["It includes testing modifiers for functions such as `set_access_id`, `set_id`, `set_kind`, `set_project_id`, `set_service_account_email`, `set_time_created`, `set_updated`, `set_etag`, and `set_state`, which are essential for mocking and testing the client library."],["The document details various methods like `access_id`, `etag`, `id`, `kind`, `project_id`, `service_account_email`, `state`, `time_created`, and `updated`, enabling developers to access and manage various attributes of an HMAC key."],["Static functions `state_active`, `state_inactive`, and `state_deleted` are provided, allowing users to easily manage and understand the different states an HMAC key can be in."]]],[]]
