Updates ALLOW_PULLS from string to boolean (quay#1402)

stevsmit · Steven Smith · web-flow · commit 2fbfe07f341d · 2025-08-14T11:29:17.000-04:00
Co-authored-by: Steven Smith &lt;stevsmit@stevsmit-thinkpadt14gen4.remote.csb&gt;
diff --git a/modules/config-debug-variables.adoc b/modules/config-debug-variables.adoc
@@ -15,7 +15,7 @@ The following variables control how {productname} logs events, exposes debugging
 Setting `USERS_DEBUG=1` exposes credentials in clear text. This variable should be removed from the {productname} deployment after debugging. The log file that is generated with this environment variable should be scrutinized, and passwords should be removed before sending to other users. Use with caution.  
 ====
 
-| **ALLOW_PULLS_WITHOUT_STRICT_LOGGING** | String | If true, pulls will still succeed even if the pull audit log entry cannot be written . This is useful if the database is in a read-only state and it is desired for pulls to continue during that time. +
+| **ALLOW_PULLS_WITHOUT_STRICT_LOGGING** | Boolean | If true, pulls will still succeed even if the pull audit log entry cannot be written . This is useful if the database is in a read-only state and it is desired for pulls to continue during that time. +
  +
  **Default:**  False
 
diff --git a/modules/config-fields-misc.adoc b/modules/config-fields-misc.adoc
@@ -6,7 +6,7 @@
 [cols="3a,1a,2a",options="header"]
 |===
 | Field | Type | Description
-| **ALLOW_PULLS_WITHOUT_STRICT_LOGGING** | String | If true, pulls will still succeed even if the pull audit log entry cannot be written . This is useful if the database is in a read-only state and it is desired for pulls to continue during that time. +
+| **ALLOW_PULLS_WITHOUT_STRICT_LOGGING** | Boolean | If true, pulls will still succeed even if the pull audit log entry cannot be written . This is useful if the database is in a read-only state and it is desired for pulls to continue during that time. +
  +
  **Default:**  False
 | **AVATAR_KIND** | String | The types of avatars to display, either generated inline (local) or Gravatar (gravatar) +

Original file line number	Diff line number	Diff line change
`@@ -15,7 +15,7 @@ The following variables control how {productname} logs events, exposes debugging`
`15`	`15`	Setting `USERS_DEBUG=1` exposes credentials in clear text. This variable should be removed from the {productname} deployment after debugging. The log file that is generated with this environment variable should be scrutinized, and passwords should be removed before sending to other users. Use with caution.
`16`	`16`	`====`
`17`	`17`
`18`		`-\| ALLOW_PULLS_WITHOUT_STRICT_LOGGING \| String \| If true, pulls will still succeed even if the pull audit log entry cannot be written . This is useful if the database is in a read-only state and it is desired for pulls to continue during that time. +`
	`18`	`+\| ALLOW_PULLS_WITHOUT_STRICT_LOGGING \| Boolean \| If true, pulls will still succeed even if the pull audit log entry cannot be written . This is useful if the database is in a read-only state and it is desired for pulls to continue during that time. +`
`19`	`19`	`+`
`20`	`20`	`Default: False`
`21`	`21`
Original file line number	Diff line number	Diff line change
`@@ -6,7 +6,7 @@`
`6`	`6`	`[cols="3a,1a,2a",options="header"]`
`7`	`7`	`\|===`
`8`	`8`	`\| Field \| Type \| Description`
`9`		`-\| ALLOW_PULLS_WITHOUT_STRICT_LOGGING \| String \| If true, pulls will still succeed even if the pull audit log entry cannot be written . This is useful if the database is in a read-only state and it is desired for pulls to continue during that time. +`
	`9`	`+\| ALLOW_PULLS_WITHOUT_STRICT_LOGGING \| Boolean \| If true, pulls will still succeed even if the pull audit log entry cannot be written . This is useful if the database is in a read-only state and it is desired for pulls to continue during that time. +`
`10`	`10`	`+`
`11`	`11`	`Default: False`
`12`	`12`	`\| AVATAR_KIND \| String \| The types of avatars to display, either generated inline (local) or Gravatar (gravatar) +`