aptible.App
Explore with Pulumi AI
Import
Existing Apps can be imported using the App ID. For example:
bash
$ pulumi import aptible:index/app:App example-app <ID>
Create App Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new App(name: string, args: AppArgs, opts?: CustomResourceOptions);
@overload
def App(resource_name: str,
args: AppArgs,
opts: Optional[ResourceOptions] = None)
@overload
def App(resource_name: str,
opts: Optional[ResourceOptions] = None,
env_id: Optional[float] = None,
handle: Optional[str] = None,
aptible_app_id: Optional[str] = None,
config: Optional[Mapping[str, str]] = None,
services: Optional[Sequence[AppServiceArgs]] = None)
func NewApp(ctx *Context, name string, args AppArgs, opts ...ResourceOption) (*App, error)
public App(string name, AppArgs args, CustomResourceOptions? opts = null)
type: aptible:App
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args AppArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args AppArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args AppArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args AppArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args AppArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var appResource = new Aptible.App("appResource", new()
{
EnvId = 0,
Handle = "string",
AptibleAppId = "string",
Config =
{
{ "string", "string" },
},
Services = new[]
{
new Aptible.Inputs.AppServiceArgs
{
AutoscalingPolicies = new[]
{
new Aptible.Inputs.AppServiceAutoscalingPolicyArgs
{
AutoscalingType = "string",
MaxContainers = 0,
MaxCpuThreshold = 0,
MaximumMemory = 0,
MemCpuRatioCThreshold = 0,
MemCpuRatioRThreshold = 0,
MemScaleDownThreshold = 0,
MemScaleUpThreshold = 0,
MetricLookbackSeconds = 0,
MinContainers = 0,
MinCpuThreshold = 0,
MinimumMemory = 0,
Percentile = 0,
PostReleaseCooldownSeconds = 0,
PostScaleDownCooldownSeconds = 0,
PostScaleUpCooldownSeconds = 0,
ScaleDownStep = 0,
ScaleUpStep = 0,
ScalingEnabled = false,
},
},
ContainerCount = 0,
ContainerMemoryLimit = 0,
ContainerProfile = "string",
ForceZeroDowntime = false,
ProcessType = "string",
SimpleHealthCheck = false,
},
},
});
example, err := aptible.NewApp(ctx, "appResource", &aptible.AppArgs{
EnvId: pulumi.Float64(0),
Handle: pulumi.String("string"),
AptibleAppId: pulumi.String("string"),
Config: pulumi.StringMap{
"string": pulumi.String("string"),
},
Services: aptible.AppServiceArray{
&aptible.AppServiceArgs{
AutoscalingPolicies: aptible.AppServiceAutoscalingPolicyArray{
&aptible.AppServiceAutoscalingPolicyArgs{
AutoscalingType: pulumi.String("string"),
MaxContainers: pulumi.Float64(0),
MaxCpuThreshold: pulumi.Float64(0),
MaximumMemory: pulumi.Float64(0),
MemCpuRatioCThreshold: pulumi.Float64(0),
MemCpuRatioRThreshold: pulumi.Float64(0),
MemScaleDownThreshold: pulumi.Float64(0),
MemScaleUpThreshold: pulumi.Float64(0),
MetricLookbackSeconds: pulumi.Float64(0),
MinContainers: pulumi.Float64(0),
MinCpuThreshold: pulumi.Float64(0),
MinimumMemory: pulumi.Float64(0),
Percentile: pulumi.Float64(0),
PostReleaseCooldownSeconds: pulumi.Float64(0),
PostScaleDownCooldownSeconds: pulumi.Float64(0),
PostScaleUpCooldownSeconds: pulumi.Float64(0),
ScaleDownStep: pulumi.Float64(0),
ScaleUpStep: pulumi.Float64(0),
ScalingEnabled: pulumi.Bool(false),
},
},
ContainerCount: pulumi.Float64(0),
ContainerMemoryLimit: pulumi.Float64(0),
ContainerProfile: pulumi.String("string"),
ForceZeroDowntime: pulumi.Bool(false),
ProcessType: pulumi.String("string"),
SimpleHealthCheck: pulumi.Bool(false),
},
},
})
var appResource = new App("appResource", AppArgs.builder()
.envId(0)
.handle("string")
.aptibleAppId("string")
.config(Map.of("string", "string"))
.services(AppServiceArgs.builder()
.autoscalingPolicies(AppServiceAutoscalingPolicyArgs.builder()
.autoscalingType("string")
.maxContainers(0)
.maxCpuThreshold(0)
.maximumMemory(0)
.memCpuRatioCThreshold(0)
.memCpuRatioRThreshold(0)
.memScaleDownThreshold(0)
.memScaleUpThreshold(0)
.metricLookbackSeconds(0)
.minContainers(0)
.minCpuThreshold(0)
.minimumMemory(0)
.percentile(0)
.postReleaseCooldownSeconds(0)
.postScaleDownCooldownSeconds(0)
.postScaleUpCooldownSeconds(0)
.scaleDownStep(0)
.scaleUpStep(0)
.scalingEnabled(false)
.build())
.containerCount(0)
.containerMemoryLimit(0)
.containerProfile("string")
.forceZeroDowntime(false)
.processType("string")
.simpleHealthCheck(false)
.build())
.build());
app_resource = aptible.App("appResource",
env_id=0,
handle="string",
aptible_app_id="string",
config={
"string": "string",
},
services=[{
"autoscaling_policies": [{
"autoscaling_type": "string",
"max_containers": 0,
"max_cpu_threshold": 0,
"maximum_memory": 0,
"mem_cpu_ratio_c_threshold": 0,
"mem_cpu_ratio_r_threshold": 0,
"mem_scale_down_threshold": 0,
"mem_scale_up_threshold": 0,
"metric_lookback_seconds": 0,
"min_containers": 0,
"min_cpu_threshold": 0,
"minimum_memory": 0,
"percentile": 0,
"post_release_cooldown_seconds": 0,
"post_scale_down_cooldown_seconds": 0,
"post_scale_up_cooldown_seconds": 0,
"scale_down_step": 0,
"scale_up_step": 0,
"scaling_enabled": False,
}],
"container_count": 0,
"container_memory_limit": 0,
"container_profile": "string",
"force_zero_downtime": False,
"process_type": "string",
"simple_health_check": False,
}])
const appResource = new aptible.App("appResource", {
envId: 0,
handle: "string",
aptibleAppId: "string",
config: {
string: "string",
},
services: [{
autoscalingPolicies: [{
autoscalingType: "string",
maxContainers: 0,
maxCpuThreshold: 0,
maximumMemory: 0,
memCpuRatioCThreshold: 0,
memCpuRatioRThreshold: 0,
memScaleDownThreshold: 0,
memScaleUpThreshold: 0,
metricLookbackSeconds: 0,
minContainers: 0,
minCpuThreshold: 0,
minimumMemory: 0,
percentile: 0,
postReleaseCooldownSeconds: 0,
postScaleDownCooldownSeconds: 0,
postScaleUpCooldownSeconds: 0,
scaleDownStep: 0,
scaleUpStep: 0,
scalingEnabled: false,
}],
containerCount: 0,
containerMemoryLimit: 0,
containerProfile: "string",
forceZeroDowntime: false,
processType: "string",
simpleHealthCheck: false,
}],
});
type: aptible:App
properties:
aptibleAppId: string
config:
string: string
envId: 0
handle: string
services:
- autoscalingPolicies:
- autoscalingType: string
maxContainers: 0
maxCpuThreshold: 0
maximumMemory: 0
memCpuRatioCThreshold: 0
memCpuRatioRThreshold: 0
memScaleDownThreshold: 0
memScaleUpThreshold: 0
metricLookbackSeconds: 0
minContainers: 0
minCpuThreshold: 0
minimumMemory: 0
percentile: 0
postReleaseCooldownSeconds: 0
postScaleDownCooldownSeconds: 0
postScaleUpCooldownSeconds: 0
scaleDownStep: 0
scaleUpStep: 0
scalingEnabled: false
containerCount: 0
containerMemoryLimit: 0
containerProfile: string
forceZeroDowntime: false
processType: string
simpleHealthCheck: false
App Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The App resource accepts the following input properties:
- Env
Id double - The ID of the environment you would like to deploy your
App in. See main provider documentation for more on how to determine what
you should use for
env_id
. - Handle string
- The handle for the App. This must be all lower case, and
only contain letters, numbers,
-
,_
, or.
- Aptible
App stringId - Config Dictionary<string, string>
- The configuration for the App. This should be a
map of
KEY = VALUE
. - Services
List<App
Service> - A block to manage scaling for services. See the main provider docs for additional details.
- Env
Id float64 - The ID of the environment you would like to deploy your
App in. See main provider documentation for more on how to determine what
you should use for
env_id
. - Handle string
- The handle for the App. This must be all lower case, and
only contain letters, numbers,
-
,_
, or.
- Aptible
App stringId - Config map[string]string
- The configuration for the App. This should be a
map of
KEY = VALUE
. - Services
[]App
Service Args - A block to manage scaling for services. See the main provider docs for additional details.
- env
Id Double - The ID of the environment you would like to deploy your
App in. See main provider documentation for more on how to determine what
you should use for
env_id
. - handle String
- The handle for the App. This must be all lower case, and
only contain letters, numbers,
-
,_
, or.
- aptible
App StringId - config Map<String,String>
- The configuration for the App. This should be a
map of
KEY = VALUE
. - services
List<App
Service> - A block to manage scaling for services. See the main provider docs for additional details.
- env
Id number - The ID of the environment you would like to deploy your
App in. See main provider documentation for more on how to determine what
you should use for
env_id
. - handle string
- The handle for the App. This must be all lower case, and
only contain letters, numbers,
-
,_
, or.
- aptible
App stringId - config {[key: string]: string}
- The configuration for the App. This should be a
map of
KEY = VALUE
. - services
App
Service[] - A block to manage scaling for services. See the main provider docs for additional details.
- env_
id float - The ID of the environment you would like to deploy your
App in. See main provider documentation for more on how to determine what
you should use for
env_id
. - handle str
- The handle for the App. This must be all lower case, and
only contain letters, numbers,
-
,_
, or.
- aptible_
app_ strid - config Mapping[str, str]
- The configuration for the App. This should be a
map of
KEY = VALUE
. - services
Sequence[App
Service Args] - A block to manage scaling for services. See the main provider docs for additional details.
- env
Id Number - The ID of the environment you would like to deploy your
App in. See main provider documentation for more on how to determine what
you should use for
env_id
. - handle String
- The handle for the App. This must be all lower case, and
only contain letters, numbers,
-
,_
, or.
- aptible
App StringId - config Map<String>
- The configuration for the App. This should be a
map of
KEY = VALUE
. - services List<Property Map>
- A block to manage scaling for services. See the main provider docs for additional details.
Outputs
All input properties are implicitly available as output properties. Additionally, the App resource produces the following output properties:
Look up Existing App Resource
Get an existing App resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: AppState, opts?: CustomResourceOptions): App
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
app_id: Optional[float] = None,
aptible_app_id: Optional[str] = None,
config: Optional[Mapping[str, str]] = None,
env_id: Optional[float] = None,
git_repo: Optional[str] = None,
handle: Optional[str] = None,
services: Optional[Sequence[AppServiceArgs]] = None) -> App
func GetApp(ctx *Context, name string, id IDInput, state *AppState, opts ...ResourceOption) (*App, error)
public static App Get(string name, Input<string> id, AppState? state, CustomResourceOptions? opts = null)
public static App get(String name, Output<String> id, AppState state, CustomResourceOptions options)
resources: _: type: aptible:App get: id: ${id}
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- App
Id double - The unique ID of the application.
- Aptible
App stringId - Config Dictionary<string, string>
- The configuration for the App. This should be a
map of
KEY = VALUE
. - Env
Id double - The ID of the environment you would like to deploy your
App in. See main provider documentation for more on how to determine what
you should use for
env_id
. - Git
Repo string - The git remote associated with the application.
- Handle string
- The handle for the App. This must be all lower case, and
only contain letters, numbers,
-
,_
, or.
- Services
List<App
Service> - A block to manage scaling for services. See the main provider docs for additional details.
- App
Id float64 - The unique ID of the application.
- Aptible
App stringId - Config map[string]string
- The configuration for the App. This should be a
map of
KEY = VALUE
. - Env
Id float64 - The ID of the environment you would like to deploy your
App in. See main provider documentation for more on how to determine what
you should use for
env_id
. - Git
Repo string - The git remote associated with the application.
- Handle string
- The handle for the App. This must be all lower case, and
only contain letters, numbers,
-
,_
, or.
- Services
[]App
Service Args - A block to manage scaling for services. See the main provider docs for additional details.
- app
Id Double - The unique ID of the application.
- aptible
App StringId - config Map<String,String>
- The configuration for the App. This should be a
map of
KEY = VALUE
. - env
Id Double - The ID of the environment you would like to deploy your
App in. See main provider documentation for more on how to determine what
you should use for
env_id
. - git
Repo String - The git remote associated with the application.
- handle String
- The handle for the App. This must be all lower case, and
only contain letters, numbers,
-
,_
, or.
- services
List<App
Service> - A block to manage scaling for services. See the main provider docs for additional details.
- app
Id number - The unique ID of the application.
- aptible
App stringId - config {[key: string]: string}
- The configuration for the App. This should be a
map of
KEY = VALUE
. - env
Id number - The ID of the environment you would like to deploy your
App in. See main provider documentation for more on how to determine what
you should use for
env_id
. - git
Repo string - The git remote associated with the application.
- handle string
- The handle for the App. This must be all lower case, and
only contain letters, numbers,
-
,_
, or.
- services
App
Service[] - A block to manage scaling for services. See the main provider docs for additional details.
- app_
id float - The unique ID of the application.
- aptible_
app_ strid - config Mapping[str, str]
- The configuration for the App. This should be a
map of
KEY = VALUE
. - env_
id float - The ID of the environment you would like to deploy your
App in. See main provider documentation for more on how to determine what
you should use for
env_id
. - git_
repo str - The git remote associated with the application.
- handle str
- The handle for the App. This must be all lower case, and
only contain letters, numbers,
-
,_
, or.
- services
Sequence[App
Service Args] - A block to manage scaling for services. See the main provider docs for additional details.
- app
Id Number - The unique ID of the application.
- aptible
App StringId - config Map<String>
- The configuration for the App. This should be a
map of
KEY = VALUE
. - env
Id Number - The ID of the environment you would like to deploy your
App in. See main provider documentation for more on how to determine what
you should use for
env_id
. - git
Repo String - The git remote associated with the application.
- handle String
- The handle for the App. This must be all lower case, and
only contain letters, numbers,
-
,_
, or.
- services List<Property Map>
- A block to manage scaling for services. See the main provider docs for additional details.
Supporting Types
AppService, AppServiceArgs
- Autoscaling
Policies List<AppService Autoscaling Policy> - A block to manage autoscaling for services. See the main provider docs for additional details.
- Container
Count double - The number of unique containers running the service.
- Container
Memory doubleLimit - The memory limit (in MB) of the service's containers.
- Container
Profile string - Changes the CPU:RAM ratio of the service's containers.
- Force
Zero boolDowntime - For services without endpoints, force
a zero-downtime release and leverage docker healthchecks for the containers. Please
note that docker healthchecks are required unless
simple_health_check
is enabled. For more information please see the docs. - Process
Type string - The
process_type
maps directly to the Service name used in the Procfile. If you are not using a Procfile, you will have a single Service with theprocess_type
ofcmd
. - Service
Sizing List<AppPolicies Service Service Sizing Policy> - Deprecated (Optional) A block to manage autoscaling for services. See the main provider docs for additional details.
- Simple
Health boolCheck - For services without endpoints, if force_zero_downtime is enabled, do a simple uptime check instead of using docker healthchecks.
- Autoscaling
Policies []AppService Autoscaling Policy - A block to manage autoscaling for services. See the main provider docs for additional details.
- Container
Count float64 - The number of unique containers running the service.
- Container
Memory float64Limit - The memory limit (in MB) of the service's containers.
- Container
Profile string - Changes the CPU:RAM ratio of the service's containers.
- Force
Zero boolDowntime - For services without endpoints, force
a zero-downtime release and leverage docker healthchecks for the containers. Please
note that docker healthchecks are required unless
simple_health_check
is enabled. For more information please see the docs. - Process
Type string - The
process_type
maps directly to the Service name used in the Procfile. If you are not using a Procfile, you will have a single Service with theprocess_type
ofcmd
. - Service
Sizing []AppPolicies Service Service Sizing Policy - Deprecated (Optional) A block to manage autoscaling for services. See the main provider docs for additional details.
- Simple
Health boolCheck - For services without endpoints, if force_zero_downtime is enabled, do a simple uptime check instead of using docker healthchecks.
- autoscaling
Policies List<AppService Autoscaling Policy> - A block to manage autoscaling for services. See the main provider docs for additional details.
- container
Count Double - The number of unique containers running the service.
- container
Memory DoubleLimit - The memory limit (in MB) of the service's containers.
- container
Profile String - Changes the CPU:RAM ratio of the service's containers.
- force
Zero BooleanDowntime - For services without endpoints, force
a zero-downtime release and leverage docker healthchecks for the containers. Please
note that docker healthchecks are required unless
simple_health_check
is enabled. For more information please see the docs. - process
Type String - The
process_type
maps directly to the Service name used in the Procfile. If you are not using a Procfile, you will have a single Service with theprocess_type
ofcmd
. - service
Sizing List<AppPolicies Service Service Sizing Policy> - Deprecated (Optional) A block to manage autoscaling for services. See the main provider docs for additional details.
- simple
Health BooleanCheck - For services without endpoints, if force_zero_downtime is enabled, do a simple uptime check instead of using docker healthchecks.
- autoscaling
Policies AppService Autoscaling Policy[] - A block to manage autoscaling for services. See the main provider docs for additional details.
- container
Count number - The number of unique containers running the service.
- container
Memory numberLimit - The memory limit (in MB) of the service's containers.
- container
Profile string - Changes the CPU:RAM ratio of the service's containers.
- force
Zero booleanDowntime - For services without endpoints, force
a zero-downtime release and leverage docker healthchecks for the containers. Please
note that docker healthchecks are required unless
simple_health_check
is enabled. For more information please see the docs. - process
Type string - The
process_type
maps directly to the Service name used in the Procfile. If you are not using a Procfile, you will have a single Service with theprocess_type
ofcmd
. - service
Sizing AppPolicies Service Service Sizing Policy[] - Deprecated (Optional) A block to manage autoscaling for services. See the main provider docs for additional details.
- simple
Health booleanCheck - For services without endpoints, if force_zero_downtime is enabled, do a simple uptime check instead of using docker healthchecks.
- autoscaling_
policies Sequence[AppService Autoscaling Policy] - A block to manage autoscaling for services. See the main provider docs for additional details.
- container_
count float - The number of unique containers running the service.
- container_
memory_ floatlimit - The memory limit (in MB) of the service's containers.
- container_
profile str - Changes the CPU:RAM ratio of the service's containers.
- force_
zero_ booldowntime - For services without endpoints, force
a zero-downtime release and leverage docker healthchecks for the containers. Please
note that docker healthchecks are required unless
simple_health_check
is enabled. For more information please see the docs. - process_
type str - The
process_type
maps directly to the Service name used in the Procfile. If you are not using a Procfile, you will have a single Service with theprocess_type
ofcmd
. - service_
sizing_ Sequence[Apppolicies Service Service Sizing Policy] - Deprecated (Optional) A block to manage autoscaling for services. See the main provider docs for additional details.
- simple_
health_ boolcheck - For services without endpoints, if force_zero_downtime is enabled, do a simple uptime check instead of using docker healthchecks.
- autoscaling
Policies List<Property Map> - A block to manage autoscaling for services. See the main provider docs for additional details.
- container
Count Number - The number of unique containers running the service.
- container
Memory NumberLimit - The memory limit (in MB) of the service's containers.
- container
Profile String - Changes the CPU:RAM ratio of the service's containers.
- force
Zero BooleanDowntime - For services without endpoints, force
a zero-downtime release and leverage docker healthchecks for the containers. Please
note that docker healthchecks are required unless
simple_health_check
is enabled. For more information please see the docs. - process
Type String - The
process_type
maps directly to the Service name used in the Procfile. If you are not using a Procfile, you will have a single Service with theprocess_type
ofcmd
. - service
Sizing List<Property Map>Policies - Deprecated (Optional) A block to manage autoscaling for services. See the main provider docs for additional details.
- simple
Health BooleanCheck - For services without endpoints, if force_zero_downtime is enabled, do a simple uptime check instead of using docker healthchecks.
AppServiceAutoscalingPolicy, AppServiceAutoscalingPolicyArgs
- Autoscaling
Type string - The type of autoscaling. Must be either
horizontal
orvertical
. - Max
Containers double - Horizontal autoscaling only - Sets the highest container count to which the service can be scaled up to by Autoscaler.
- Max
Cpu doubleThreshold - Horizontal autoscaling only - Specifies the percentage of the current CPU usage at which an up-scaling action is triggered.
- Maximum
Memory double - Vertical autoscaling only - Defines the upper memory threshold, capping the maximum memory allocation possible through Autoscaler. If blank, the container can scale to the largest size available.
- Mem
Cpu doubleRatio CThreshold - Sets the Memory-to-CPU ratio threshold, below which the service is transitioned to a C (Compute Optimized) profile.
- Mem
Cpu doubleRatio RThreshold - Establishes the ratio of Memory (in GB) to CPU (in CPUs) at which values exceeding the threshold prompt a shift to an R (Memory Optimized) profile.
- Mem
Scale doubleDown Threshold - Vertical autoscaling only - Specifies the percentage of the current memory limit at which the service’s memory usage triggers a down-scaling action.
- Mem
Scale doubleUp Threshold - Vertical autoscaling only - Specifies the percentage of the current memory limit at which the service’s memory usage triggers an up-scaling action.
- Metric
Lookback doubleSeconds - The duration in seconds for retrieving past performance metrics.
- Min
Containers double - Horizontal autoscaling only - Sets the lowest container count to which the service can be scaled down by Autoscaler.
- Min
Cpu doubleThreshold - Horizontal autoscaling only - Specifies the percentage of the current CPU usage at which a down-scaling action is triggered.
- Minimum
Memory double - Vertical autoscaling only - Sets the lowest memory limit to which the service can be scaled down by Autoscaler.
- Percentile double
- The percentile for evaluating metrics.
- Post
Release doubleCooldown Seconds - The time in seconds to ignore in metrics following a deploy to allow for service stabilization.
- Post
Scale doubleDown Cooldown Seconds - The waiting period in seconds after an automated scale-down before another scaling action can be considered.
- Post
Scale doubleUp Cooldown Seconds - The waiting period in seconds after an automated scale-up before another scaling action can be considered.
- Scale
Down doubleStep - Horizontal autoscaling only - Sets the amount of containers to remove when autoscaling (ex: a value of 2 will go from 4->2->1). Container count will never exceed the configured minimum.
- Scale
Up doubleStep - Horizontal autoscaling only - Sets the amount of containers to add when autoscaling (ex: a value of 2 will go from 1->3->5). Container count will never exceed the configured maximum.
- Scaling
Enabled bool
- Autoscaling
Type string - The type of autoscaling. Must be either
horizontal
orvertical
. - Max
Containers float64 - Horizontal autoscaling only - Sets the highest container count to which the service can be scaled up to by Autoscaler.
- Max
Cpu float64Threshold - Horizontal autoscaling only - Specifies the percentage of the current CPU usage at which an up-scaling action is triggered.
- Maximum
Memory float64 - Vertical autoscaling only - Defines the upper memory threshold, capping the maximum memory allocation possible through Autoscaler. If blank, the container can scale to the largest size available.
- Mem
Cpu float64Ratio CThreshold - Sets the Memory-to-CPU ratio threshold, below which the service is transitioned to a C (Compute Optimized) profile.
- Mem
Cpu float64Ratio RThreshold - Establishes the ratio of Memory (in GB) to CPU (in CPUs) at which values exceeding the threshold prompt a shift to an R (Memory Optimized) profile.
- Mem
Scale float64Down Threshold - Vertical autoscaling only - Specifies the percentage of the current memory limit at which the service’s memory usage triggers a down-scaling action.
- Mem
Scale float64Up Threshold - Vertical autoscaling only - Specifies the percentage of the current memory limit at which the service’s memory usage triggers an up-scaling action.
- Metric
Lookback float64Seconds - The duration in seconds for retrieving past performance metrics.
- Min
Containers float64 - Horizontal autoscaling only - Sets the lowest container count to which the service can be scaled down by Autoscaler.
- Min
Cpu float64Threshold - Horizontal autoscaling only - Specifies the percentage of the current CPU usage at which a down-scaling action is triggered.
- Minimum
Memory float64 - Vertical autoscaling only - Sets the lowest memory limit to which the service can be scaled down by Autoscaler.
- Percentile float64
- The percentile for evaluating metrics.
- Post
Release float64Cooldown Seconds - The time in seconds to ignore in metrics following a deploy to allow for service stabilization.
- Post
Scale float64Down Cooldown Seconds - The waiting period in seconds after an automated scale-down before another scaling action can be considered.
- Post
Scale float64Up Cooldown Seconds - The waiting period in seconds after an automated scale-up before another scaling action can be considered.
- Scale
Down float64Step - Horizontal autoscaling only - Sets the amount of containers to remove when autoscaling (ex: a value of 2 will go from 4->2->1). Container count will never exceed the configured minimum.
- Scale
Up float64Step - Horizontal autoscaling only - Sets the amount of containers to add when autoscaling (ex: a value of 2 will go from 1->3->5). Container count will never exceed the configured maximum.
- Scaling
Enabled bool
- autoscaling
Type String - The type of autoscaling. Must be either
horizontal
orvertical
. - max
Containers Double - Horizontal autoscaling only - Sets the highest container count to which the service can be scaled up to by Autoscaler.
- max
Cpu DoubleThreshold - Horizontal autoscaling only - Specifies the percentage of the current CPU usage at which an up-scaling action is triggered.
- maximum
Memory Double - Vertical autoscaling only - Defines the upper memory threshold, capping the maximum memory allocation possible through Autoscaler. If blank, the container can scale to the largest size available.
- mem
Cpu DoubleRatio CThreshold - Sets the Memory-to-CPU ratio threshold, below which the service is transitioned to a C (Compute Optimized) profile.
- mem
Cpu DoubleRatio RThreshold - Establishes the ratio of Memory (in GB) to CPU (in CPUs) at which values exceeding the threshold prompt a shift to an R (Memory Optimized) profile.
- mem
Scale DoubleDown Threshold - Vertical autoscaling only - Specifies the percentage of the current memory limit at which the service’s memory usage triggers a down-scaling action.
- mem
Scale DoubleUp Threshold - Vertical autoscaling only - Specifies the percentage of the current memory limit at which the service’s memory usage triggers an up-scaling action.
- metric
Lookback DoubleSeconds - The duration in seconds for retrieving past performance metrics.
- min
Containers Double - Horizontal autoscaling only - Sets the lowest container count to which the service can be scaled down by Autoscaler.
- min
Cpu DoubleThreshold - Horizontal autoscaling only - Specifies the percentage of the current CPU usage at which a down-scaling action is triggered.
- minimum
Memory Double - Vertical autoscaling only - Sets the lowest memory limit to which the service can be scaled down by Autoscaler.
- percentile Double
- The percentile for evaluating metrics.
- post
Release DoubleCooldown Seconds - The time in seconds to ignore in metrics following a deploy to allow for service stabilization.
- post
Scale DoubleDown Cooldown Seconds - The waiting period in seconds after an automated scale-down before another scaling action can be considered.
- post
Scale DoubleUp Cooldown Seconds - The waiting period in seconds after an automated scale-up before another scaling action can be considered.
- scale
Down DoubleStep - Horizontal autoscaling only - Sets the amount of containers to remove when autoscaling (ex: a value of 2 will go from 4->2->1). Container count will never exceed the configured minimum.
- scale
Up DoubleStep - Horizontal autoscaling only - Sets the amount of containers to add when autoscaling (ex: a value of 2 will go from 1->3->5). Container count will never exceed the configured maximum.
- scaling
Enabled Boolean
- autoscaling
Type string - The type of autoscaling. Must be either
horizontal
orvertical
. - max
Containers number - Horizontal autoscaling only - Sets the highest container count to which the service can be scaled up to by Autoscaler.
- max
Cpu numberThreshold - Horizontal autoscaling only - Specifies the percentage of the current CPU usage at which an up-scaling action is triggered.
- maximum
Memory number - Vertical autoscaling only - Defines the upper memory threshold, capping the maximum memory allocation possible through Autoscaler. If blank, the container can scale to the largest size available.
- mem
Cpu numberRatio CThreshold - Sets the Memory-to-CPU ratio threshold, below which the service is transitioned to a C (Compute Optimized) profile.
- mem
Cpu numberRatio RThreshold - Establishes the ratio of Memory (in GB) to CPU (in CPUs) at which values exceeding the threshold prompt a shift to an R (Memory Optimized) profile.
- mem
Scale numberDown Threshold - Vertical autoscaling only - Specifies the percentage of the current memory limit at which the service’s memory usage triggers a down-scaling action.
- mem
Scale numberUp Threshold - Vertical autoscaling only - Specifies the percentage of the current memory limit at which the service’s memory usage triggers an up-scaling action.
- metric
Lookback numberSeconds - The duration in seconds for retrieving past performance metrics.
- min
Containers number - Horizontal autoscaling only - Sets the lowest container count to which the service can be scaled down by Autoscaler.
- min
Cpu numberThreshold - Horizontal autoscaling only - Specifies the percentage of the current CPU usage at which a down-scaling action is triggered.
- minimum
Memory number - Vertical autoscaling only - Sets the lowest memory limit to which the service can be scaled down by Autoscaler.
- percentile number
- The percentile for evaluating metrics.
- post
Release numberCooldown Seconds - The time in seconds to ignore in metrics following a deploy to allow for service stabilization.
- post
Scale numberDown Cooldown Seconds - The waiting period in seconds after an automated scale-down before another scaling action can be considered.
- post
Scale numberUp Cooldown Seconds - The waiting period in seconds after an automated scale-up before another scaling action can be considered.
- scale
Down numberStep - Horizontal autoscaling only - Sets the amount of containers to remove when autoscaling (ex: a value of 2 will go from 4->2->1). Container count will never exceed the configured minimum.
- scale
Up numberStep - Horizontal autoscaling only - Sets the amount of containers to add when autoscaling (ex: a value of 2 will go from 1->3->5). Container count will never exceed the configured maximum.
- scaling
Enabled boolean
- autoscaling_
type str - The type of autoscaling. Must be either
horizontal
orvertical
. - max_
containers float - Horizontal autoscaling only - Sets the highest container count to which the service can be scaled up to by Autoscaler.
- max_
cpu_ floatthreshold - Horizontal autoscaling only - Specifies the percentage of the current CPU usage at which an up-scaling action is triggered.
- maximum_
memory float - Vertical autoscaling only - Defines the upper memory threshold, capping the maximum memory allocation possible through Autoscaler. If blank, the container can scale to the largest size available.
- mem_
cpu_ floatratio_ c_ threshold - Sets the Memory-to-CPU ratio threshold, below which the service is transitioned to a C (Compute Optimized) profile.
- mem_
cpu_ floatratio_ r_ threshold - Establishes the ratio of Memory (in GB) to CPU (in CPUs) at which values exceeding the threshold prompt a shift to an R (Memory Optimized) profile.
- mem_
scale_ floatdown_ threshold - Vertical autoscaling only - Specifies the percentage of the current memory limit at which the service’s memory usage triggers a down-scaling action.
- mem_
scale_ floatup_ threshold - Vertical autoscaling only - Specifies the percentage of the current memory limit at which the service’s memory usage triggers an up-scaling action.
- metric_
lookback_ floatseconds - The duration in seconds for retrieving past performance metrics.
- min_
containers float - Horizontal autoscaling only - Sets the lowest container count to which the service can be scaled down by Autoscaler.
- min_
cpu_ floatthreshold - Horizontal autoscaling only - Specifies the percentage of the current CPU usage at which a down-scaling action is triggered.
- minimum_
memory float - Vertical autoscaling only - Sets the lowest memory limit to which the service can be scaled down by Autoscaler.
- percentile float
- The percentile for evaluating metrics.
- post_
release_ floatcooldown_ seconds - The time in seconds to ignore in metrics following a deploy to allow for service stabilization.
- post_
scale_ floatdown_ cooldown_ seconds - The waiting period in seconds after an automated scale-down before another scaling action can be considered.
- post_
scale_ floatup_ cooldown_ seconds - The waiting period in seconds after an automated scale-up before another scaling action can be considered.
- scale_
down_ floatstep - Horizontal autoscaling only - Sets the amount of containers to remove when autoscaling (ex: a value of 2 will go from 4->2->1). Container count will never exceed the configured minimum.
- scale_
up_ floatstep - Horizontal autoscaling only - Sets the amount of containers to add when autoscaling (ex: a value of 2 will go from 1->3->5). Container count will never exceed the configured maximum.
- scaling_
enabled bool
- autoscaling
Type String - The type of autoscaling. Must be either
horizontal
orvertical
. - max
Containers Number - Horizontal autoscaling only - Sets the highest container count to which the service can be scaled up to by Autoscaler.
- max
Cpu NumberThreshold - Horizontal autoscaling only - Specifies the percentage of the current CPU usage at which an up-scaling action is triggered.
- maximum
Memory Number - Vertical autoscaling only - Defines the upper memory threshold, capping the maximum memory allocation possible through Autoscaler. If blank, the container can scale to the largest size available.
- mem
Cpu NumberRatio CThreshold - Sets the Memory-to-CPU ratio threshold, below which the service is transitioned to a C (Compute Optimized) profile.
- mem
Cpu NumberRatio RThreshold - Establishes the ratio of Memory (in GB) to CPU (in CPUs) at which values exceeding the threshold prompt a shift to an R (Memory Optimized) profile.
- mem
Scale NumberDown Threshold - Vertical autoscaling only - Specifies the percentage of the current memory limit at which the service’s memory usage triggers a down-scaling action.
- mem
Scale NumberUp Threshold - Vertical autoscaling only - Specifies the percentage of the current memory limit at which the service’s memory usage triggers an up-scaling action.
- metric
Lookback NumberSeconds - The duration in seconds for retrieving past performance metrics.
- min
Containers Number - Horizontal autoscaling only - Sets the lowest container count to which the service can be scaled down by Autoscaler.
- min
Cpu NumberThreshold - Horizontal autoscaling only - Specifies the percentage of the current CPU usage at which a down-scaling action is triggered.
- minimum
Memory Number - Vertical autoscaling only - Sets the lowest memory limit to which the service can be scaled down by Autoscaler.
- percentile Number
- The percentile for evaluating metrics.
- post
Release NumberCooldown Seconds - The time in seconds to ignore in metrics following a deploy to allow for service stabilization.
- post
Scale NumberDown Cooldown Seconds - The waiting period in seconds after an automated scale-down before another scaling action can be considered.
- post
Scale NumberUp Cooldown Seconds - The waiting period in seconds after an automated scale-up before another scaling action can be considered.
- scale
Down NumberStep - Horizontal autoscaling only - Sets the amount of containers to remove when autoscaling (ex: a value of 2 will go from 4->2->1). Container count will never exceed the configured minimum.
- scale
Up NumberStep - Horizontal autoscaling only - Sets the amount of containers to add when autoscaling (ex: a value of 2 will go from 1->3->5). Container count will never exceed the configured maximum.
- scaling
Enabled Boolean
AppServiceServiceSizingPolicy, AppServiceServiceSizingPolicyArgs
- Autoscaling
Type string - The type of autoscaling, must be either 'vertical' or 'horizontal'.
- Max
Containers double - The maximum number of containers for scaling.
- Max
Cpu doubleThreshold - The maximum CPU utilization threshold for scaling.
- Maximum
Memory double - The maximum memory allocation in MB.
- Mem
Cpu doubleRatio CThreshold - Sets the Memory-to-CPU ratio threshold, below which the service is transitioned to a C (Compute Optimized) profile.
- Mem
Cpu doubleRatio RThreshold - Establishes the ratio of Memory (in GB) to CPU (in CPUs) at which values exceeding the threshold prompt a shift to an R (Memory Optimized) profile.
- Mem
Scale doubleDown Threshold - The memory usage threshold for scaling down.
- Mem
Scale doubleUp Threshold - The memory usage threshold for scaling up.
- Metric
Lookback doubleSeconds - The lookback period for metrics in seconds.
- Min
Containers double - The minimum number of containers for scaling.
- Min
Cpu doubleThreshold - The minimum CPU utilization threshold for scaling.
- Minimum
Memory double - The minimum memory allocation in MB.
- Percentile double
- The percentile threshold used for scaling.
- Post
Release doubleCooldown Seconds - Seconds to ignore in metrics after a release event.
- Post
Scale doubleDown Cooldown Seconds - Cooldown period in seconds after a scale-down event.
- Post
Scale doubleUp Cooldown Seconds - Cooldown period in seconds after a scale-up event.
- Scale
Down doubleStep - The number of containers to remove in each scale-down event.
- Scale
Up doubleStep - The number of containers to add in each scale-up event.
- Scaling
Enabled bool
- Autoscaling
Type string - The type of autoscaling, must be either 'vertical' or 'horizontal'.
- Max
Containers float64 - The maximum number of containers for scaling.
- Max
Cpu float64Threshold - The maximum CPU utilization threshold for scaling.
- Maximum
Memory float64 - The maximum memory allocation in MB.
- Mem
Cpu float64Ratio CThreshold - Sets the Memory-to-CPU ratio threshold, below which the service is transitioned to a C (Compute Optimized) profile.
- Mem
Cpu float64Ratio RThreshold - Establishes the ratio of Memory (in GB) to CPU (in CPUs) at which values exceeding the threshold prompt a shift to an R (Memory Optimized) profile.
- Mem
Scale float64Down Threshold - The memory usage threshold for scaling down.
- Mem
Scale float64Up Threshold - The memory usage threshold for scaling up.
- Metric
Lookback float64Seconds - The lookback period for metrics in seconds.
- Min
Containers float64 - The minimum number of containers for scaling.
- Min
Cpu float64Threshold - The minimum CPU utilization threshold for scaling.
- Minimum
Memory float64 - The minimum memory allocation in MB.
- Percentile float64
- The percentile threshold used for scaling.
- Post
Release float64Cooldown Seconds - Seconds to ignore in metrics after a release event.
- Post
Scale float64Down Cooldown Seconds - Cooldown period in seconds after a scale-down event.
- Post
Scale float64Up Cooldown Seconds - Cooldown period in seconds after a scale-up event.
- Scale
Down float64Step - The number of containers to remove in each scale-down event.
- Scale
Up float64Step - The number of containers to add in each scale-up event.
- Scaling
Enabled bool
- autoscaling
Type String - The type of autoscaling, must be either 'vertical' or 'horizontal'.
- max
Containers Double - The maximum number of containers for scaling.
- max
Cpu DoubleThreshold - The maximum CPU utilization threshold for scaling.
- maximum
Memory Double - The maximum memory allocation in MB.
- mem
Cpu DoubleRatio CThreshold - Sets the Memory-to-CPU ratio threshold, below which the service is transitioned to a C (Compute Optimized) profile.
- mem
Cpu DoubleRatio RThreshold - Establishes the ratio of Memory (in GB) to CPU (in CPUs) at which values exceeding the threshold prompt a shift to an R (Memory Optimized) profile.
- mem
Scale DoubleDown Threshold - The memory usage threshold for scaling down.
- mem
Scale DoubleUp Threshold - The memory usage threshold for scaling up.
- metric
Lookback DoubleSeconds - The lookback period for metrics in seconds.
- min
Containers Double - The minimum number of containers for scaling.
- min
Cpu DoubleThreshold - The minimum CPU utilization threshold for scaling.
- minimum
Memory Double - The minimum memory allocation in MB.
- percentile Double
- The percentile threshold used for scaling.
- post
Release DoubleCooldown Seconds - Seconds to ignore in metrics after a release event.
- post
Scale DoubleDown Cooldown Seconds - Cooldown period in seconds after a scale-down event.
- post
Scale DoubleUp Cooldown Seconds - Cooldown period in seconds after a scale-up event.
- scale
Down DoubleStep - The number of containers to remove in each scale-down event.
- scale
Up DoubleStep - The number of containers to add in each scale-up event.
- scaling
Enabled Boolean
- autoscaling
Type string - The type of autoscaling, must be either 'vertical' or 'horizontal'.
- max
Containers number - The maximum number of containers for scaling.
- max
Cpu numberThreshold - The maximum CPU utilization threshold for scaling.
- maximum
Memory number - The maximum memory allocation in MB.
- mem
Cpu numberRatio CThreshold - Sets the Memory-to-CPU ratio threshold, below which the service is transitioned to a C (Compute Optimized) profile.
- mem
Cpu numberRatio RThreshold - Establishes the ratio of Memory (in GB) to CPU (in CPUs) at which values exceeding the threshold prompt a shift to an R (Memory Optimized) profile.
- mem
Scale numberDown Threshold - The memory usage threshold for scaling down.
- mem
Scale numberUp Threshold - The memory usage threshold for scaling up.
- metric
Lookback numberSeconds - The lookback period for metrics in seconds.
- min
Containers number - The minimum number of containers for scaling.
- min
Cpu numberThreshold - The minimum CPU utilization threshold for scaling.
- minimum
Memory number - The minimum memory allocation in MB.
- percentile number
- The percentile threshold used for scaling.
- post
Release numberCooldown Seconds - Seconds to ignore in metrics after a release event.
- post
Scale numberDown Cooldown Seconds - Cooldown period in seconds after a scale-down event.
- post
Scale numberUp Cooldown Seconds - Cooldown period in seconds after a scale-up event.
- scale
Down numberStep - The number of containers to remove in each scale-down event.
- scale
Up numberStep - The number of containers to add in each scale-up event.
- scaling
Enabled boolean
- autoscaling_
type str - The type of autoscaling, must be either 'vertical' or 'horizontal'.
- max_
containers float - The maximum number of containers for scaling.
- max_
cpu_ floatthreshold - The maximum CPU utilization threshold for scaling.
- maximum_
memory float - The maximum memory allocation in MB.
- mem_
cpu_ floatratio_ c_ threshold - Sets the Memory-to-CPU ratio threshold, below which the service is transitioned to a C (Compute Optimized) profile.
- mem_
cpu_ floatratio_ r_ threshold - Establishes the ratio of Memory (in GB) to CPU (in CPUs) at which values exceeding the threshold prompt a shift to an R (Memory Optimized) profile.
- mem_
scale_ floatdown_ threshold - The memory usage threshold for scaling down.
- mem_
scale_ floatup_ threshold - The memory usage threshold for scaling up.
- metric_
lookback_ floatseconds - The lookback period for metrics in seconds.
- min_
containers float - The minimum number of containers for scaling.
- min_
cpu_ floatthreshold - The minimum CPU utilization threshold for scaling.
- minimum_
memory float - The minimum memory allocation in MB.
- percentile float
- The percentile threshold used for scaling.
- post_
release_ floatcooldown_ seconds - Seconds to ignore in metrics after a release event.
- post_
scale_ floatdown_ cooldown_ seconds - Cooldown period in seconds after a scale-down event.
- post_
scale_ floatup_ cooldown_ seconds - Cooldown period in seconds after a scale-up event.
- scale_
down_ floatstep - The number of containers to remove in each scale-down event.
- scale_
up_ floatstep - The number of containers to add in each scale-up event.
- scaling_
enabled bool
- autoscaling
Type String - The type of autoscaling, must be either 'vertical' or 'horizontal'.
- max
Containers Number - The maximum number of containers for scaling.
- max
Cpu NumberThreshold - The maximum CPU utilization threshold for scaling.
- maximum
Memory Number - The maximum memory allocation in MB.
- mem
Cpu NumberRatio CThreshold - Sets the Memory-to-CPU ratio threshold, below which the service is transitioned to a C (Compute Optimized) profile.
- mem
Cpu NumberRatio RThreshold - Establishes the ratio of Memory (in GB) to CPU (in CPUs) at which values exceeding the threshold prompt a shift to an R (Memory Optimized) profile.
- mem
Scale NumberDown Threshold - The memory usage threshold for scaling down.
- mem
Scale NumberUp Threshold - The memory usage threshold for scaling up.
- metric
Lookback NumberSeconds - The lookback period for metrics in seconds.
- min
Containers Number - The minimum number of containers for scaling.
- min
Cpu NumberThreshold - The minimum CPU utilization threshold for scaling.
- minimum
Memory Number - The minimum memory allocation in MB.
- percentile Number
- The percentile threshold used for scaling.
- post
Release NumberCooldown Seconds - Seconds to ignore in metrics after a release event.
- post
Scale NumberDown Cooldown Seconds - Cooldown period in seconds after a scale-down event.
- post
Scale NumberUp Cooldown Seconds - Cooldown period in seconds after a scale-up event.
- scale
Down NumberStep - The number of containers to remove in each scale-down event.
- scale
Up NumberStep - The number of containers to add in each scale-up event.
- scaling
Enabled Boolean
Package Details
- Repository
- aptible aptible/terraform-provider-aptible
- License
- Notes
- This Pulumi package is based on the
aptible
Terraform Provider.