Boolean value indicating if split health checks should be used instead
of the legacy health checks. At an app.yaml level, this means defaulting
to 'readiness_check' and 'liveness_check' values instead of
'health_check' ones. Once the legacy 'health_check' behavior is
deprecated, and this value is always true, this setting can
be removed.
Boolean value indicating if split health checks should be used instead
of the legacy health checks. At an app.yaml level, this means defaulting
to 'readiness_check' and 'liveness_check' values instead of
'health_check' ones. Once the legacy 'health_check' behavior is
deprecated, and this value is always true, this setting can
be removed.
Boolean value indicating if split health checks should be used instead
of the legacy health checks. At an app.yaml level, this means defaulting
to 'readiness_check' and 'liveness_check' values instead of
'health_check' ones. Once the legacy 'health_check' behavior is
deprecated, and this value is always true, this setting can
be removed.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-02-27 UTC."],[],[]]