Class CapacityTaskTimeoutsArgs.Builder

  • Enclosing class:
    CapacityTaskTimeoutsArgs

    public static final class CapacityTaskTimeoutsArgs.Builder
    extends java.lang.Object
    • Method Detail

      • create

        public CapacityTaskTimeoutsArgs.Builder create​(@Nullable
                                                       com.pulumi.core.Output<java.lang.String> create)
        Parameters:
        create - A string that can be [parsed as a duration](https://pkg.go.dev/time#ParseDuration) consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
        Returns:
        builder
      • create

        public CapacityTaskTimeoutsArgs.Builder create​(java.lang.String create)
        Parameters:
        create - A string that can be [parsed as a duration](https://pkg.go.dev/time#ParseDuration) consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
        Returns:
        builder
      • delete

        public CapacityTaskTimeoutsArgs.Builder delete​(@Nullable
                                                       com.pulumi.core.Output<java.lang.String> delete)
        Parameters:
        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:
        Returns:
        builder
      • delete

        public CapacityTaskTimeoutsArgs.Builder delete​(java.lang.String delete)
        Parameters:
        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:
        Returns:
        builder