CapacityTaskTimeouts class
Constructors
-
CapacityTaskTimeouts({Input<String?>? create, Input<String?>? delete})
-
Creates a new CapacityTaskTimeouts.
create A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
delete > Long-running capacity tasks. The default create timeout of 60m is sufficient for most re-balancing operations on small to medium instance types. However, capacity tasks that change the configuration of bare-metal instance types (*.metal) or very large instance types (24xlarge, 48xlarge, etc.) in the current or target state can take 8 to 12 hours to complete, because AWS must stop, reconfigure, and re-start the underlying hardware. If your instancePool configuration or the current state of the Outpost involves one of these instance types, override the create timeout accordingly — for example:
const
-
CapacityTaskTimeouts.fromMap(Map<String, dynamic> map)
-
factory
Properties
-
create
→ Input<String?>?
-
A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
final
-
delete
→ Input<String?>?
-
> Long-running capacity tasks. The default
create timeout of 60m is sufficient for most re-balancing operations on small to medium instance types. However, capacity tasks that change the configuration of bare-metal instance types (*.metal) or very large instance types (24xlarge, 48xlarge, etc.) in the current or target state can take 8 to 12 hours to complete, because AWS must stop, reconfigure, and re-start the underlying hardware. If your instancePool configuration or the current state of the Outpost involves one of these instance types, override the create timeout accordingly — for example:
final
-
hashCode
→ int
-
The hash code for this object.
no setterinherited
-
runtimeType
→ Type
-
A representation of the runtime type of the object.
no setterinherited