From ca228c85921f6fe8bfabee719f8a934ee3f97d8f Mon Sep 17 00:00:00 2001
From: Josh Schneier <josh.schneier@gmail.com>
Date: Thu, 22 Dec 2022 18:56:47 -0800
Subject: [PATCH] [docs/gcloud] add caveat about maximum value of GS_EXPIRATION
 in v4 (#1202)

Co-authored-by: Shahbaz Khan <shahbazkhan185@gmail.com>
---
 docs/backends/gcloud.rst | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/backends/gcloud.rst b/docs/backends/gcloud.rst
index 9a87ef36a..49c0aa1bf 100644
--- a/docs/backends/gcloud.rst
+++ b/docs/backends/gcloud.rst
@@ -204,6 +204,7 @@ Note: Default Google Compute Engine (GCE) Service accounts are
 The ``GS_EXPIRATION`` value is handled by the underlying `Google library  <https://googlecloudplatform.github.io/google-cloud-python/latest/storage/blobs.html#google.cloud.storage.blob.Blob.generate_signed_url>`_.
 It supports `timedelta`, `datetime`, or `integer` seconds since epoch time.
 
+Note: The maximum value for this option is 7 days (604800 seconds) in version `v4` (See this `Github issue  <https://github.com/googleapis/python-storage/issues/456#issuecomment-856884993>`_)
 
 Usage
 -----