Reference documentation and code samples for the Google Cloud Appengine Admin V1 Client class FeatureSettings.
The feature specific settings to be used in the application. These define
behaviors that are user configurable.
Generated from protobuf message google.appengine.v1.Application.FeatureSettings
Namespace
Google \ Cloud \ AppEngine \ V1 \ Application
Methods
__construct
Constructor.
Parameters
Name
Description
data
array
Optional. Data for populating the Message object.
↳ split_health_checks
bool
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.
↳ use_container_optimized_os
bool
If true, use Container-Optimized OS base image for VMs, rather than a base Debian image.
getSplitHealthChecks
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.
Returns
Type
Description
bool
setSplitHealthChecks
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.
Parameter
Name
Description
var
bool
Returns
Type
Description
$this
getUseContainerOptimizedOs
If true, use Container-Optimized OS
base image for VMs, rather than a base Debian image.
Returns
Type
Description
bool
setUseContainerOptimizedOs
If true, use Container-Optimized OS
base image for VMs, rather than a base Debian image.
[[["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-09-04 UTC."],[],[],null,["# Google Cloud Appengine Admin V1 Client - Class FeatureSettings (2.0.4)\n\nVersion latestkeyboard_arrow_down\n\n- [2.0.4 (latest)](/php/docs/reference/cloud-appengine-admin/latest/V1.Application.FeatureSettings)\n- [2.0.3](/php/docs/reference/cloud-appengine-admin/2.0.3/V1.Application.FeatureSettings)\n- [1.3.5](/php/docs/reference/cloud-appengine-admin/1.3.5/V1.Application.FeatureSettings)\n- [1.2.2](/php/docs/reference/cloud-appengine-admin/1.2.2/V1.Application.FeatureSettings)\n- [1.1.1](/php/docs/reference/cloud-appengine-admin/1.1.1/V1.Application.FeatureSettings)\n- [1.0.6](/php/docs/reference/cloud-appengine-admin/1.0.6/V1.Application.FeatureSettings) \nReference documentation and code samples for the Google Cloud Appengine Admin V1 Client class FeatureSettings.\n\nThe feature specific settings to be used in the application. These define\nbehaviors that are user configurable.\n\nGenerated from protobuf message `google.appengine.v1.Application.FeatureSettings`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ AppEngine \\\\ V1 \\\\ Application\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getSplitHealthChecks\n\nBoolean value indicating if split health checks should be used instead\nof the legacy health checks. At an app.yaml level, this means defaulting\nto 'readiness_check' and 'liveness_check' values instead of\n'health_check' ones. Once the legacy 'health_check' behavior is\ndeprecated, and this value is always true, this setting can\nbe removed.\n\n### setSplitHealthChecks\n\nBoolean value indicating if split health checks should be used instead\nof the legacy health checks. At an app.yaml level, this means defaulting\nto 'readiness_check' and 'liveness_check' values instead of\n'health_check' ones. Once the legacy 'health_check' behavior is\ndeprecated, and this value is always true, this setting can\nbe removed.\n\n### getUseContainerOptimizedOs\n\nIf true, use [Container-Optimized OS](https://cloud.google.com/container-optimized-os/)\nbase image for VMs, rather than a base Debian image.\n\n### setUseContainerOptimizedOs\n\nIf true, use [Container-Optimized OS](https://cloud.google.com/container-optimized-os/)\nbase image for VMs, rather than a base Debian image."]]
