com.pulumi.azurenative.signalrservice.inputs.ServerlessSettingsArgs Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of azure-native Show documentation
Show all versions of azure-native Show documentation
A native Pulumi package for creating and managing Azure resources.
// *** WARNING: this file was generated by pulumi-java-gen. ***
// *** Do not edit by hand unless you're certain you know what you are doing! ***
package com.pulumi.azurenative.signalrservice.inputs;
import com.pulumi.core.Output;
import com.pulumi.core.annotations.Import;
import com.pulumi.core.internal.Codegen;
import java.lang.Integer;
import java.util.Objects;
import java.util.Optional;
import javax.annotation.Nullable;
/**
* Serverless settings.
*
*/
public final class ServerlessSettingsArgs extends com.pulumi.resources.ResourceArgs {
public static final ServerlessSettingsArgs Empty = new ServerlessSettingsArgs();
/**
* Gets or sets Client Connection Timeout. Optional to be set.
* Value in seconds.
* Default value is 30 seconds.
* Customer should set the timeout to a shorter period if messages are expected to be sent in shorter intervals,
* and want the client to disconnect more quickly after the last message is sent.
* You can set the timeout to a longer period if messages are expected to be sent in longer intervals,
* and they want to keep the same client connection alive during this session.
* The service considers the client disconnected if it hasn't received a message (including keep-alive) in this interval.
*
*/
@Import(name="connectionTimeoutInSeconds")
private @Nullable Output connectionTimeoutInSeconds;
/**
* @return Gets or sets Client Connection Timeout. Optional to be set.
* Value in seconds.
* Default value is 30 seconds.
* Customer should set the timeout to a shorter period if messages are expected to be sent in shorter intervals,
* and want the client to disconnect more quickly after the last message is sent.
* You can set the timeout to a longer period if messages are expected to be sent in longer intervals,
* and they want to keep the same client connection alive during this session.
* The service considers the client disconnected if it hasn't received a message (including keep-alive) in this interval.
*
*/
public Optional
© 2015 - 2024 Weber Informatics LLC | Privacy Policy