pulumi-azure-kotlin/com.pulumi.azure.arcmachine.kotlin/ExtensionArgs

ExtensionArgs

data class ExtensionArgs(val arcMachineId: Output<String>? = null, val automaticUpgradeEnabled: Output<Boolean>? = null, val forceUpdateTag: Output<String>? = null, val location: Output<String>? = null, val name: Output<String>? = null, val protectedSettings: Output<String>? = null, val publisher: Output<String>? = null, val settings: Output<String>? = null, val tags: Output<Map<String, String>>? = null, val type: Output<String>? = null, val typeHandlerVersion: Output<String>? = null) : ConvertibleToJava<ExtensionArgs>

Manages a Hybrid Compute Machine Extension.

Import

Hybrid Compute Machine Extensions can be imported using the resource id, e.g.

$ pulumi import azure:arcmachine/extension:Extension example /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/group1/providers/Microsoft.HybridCompute/machines/hcmachine1/extensions/ext1

Constructors

ExtensionArgs

fun ExtensionArgs(arcMachineId: Output<String>? = null, automaticUpgradeEnabled: Output<Boolean>? = null, forceUpdateTag: Output<String>? = null, location: Output<String>? = null, name: Output<String>? = null, protectedSettings: Output<String>? = null, publisher: Output<String>? = null, settings: Output<String>? = null, tags: Output<Map<String, String>>? = null, type: Output<String>? = null, typeHandlerVersion: Output<String>? = null)

Functions

toJava

open override fun toJava(): ExtensionArgs

Properties

arcMachineId

val arcMachineId: Output<String>? = null

The ID of the Hybrid Compute Machine Extension. Changing this forces a new Hybrid Compute Machine Extension to be created.

automaticUpgradeEnabled

val automaticUpgradeEnabled: Output<Boolean>? = null

Indicates whether the extension should be automatically upgraded by the platform if there is a newer version available. Supported values are true and false. NOTE: When automatic_upgrade_enabled can only be set during creation. Any later change will be ignored. NOTE: When automatic_upgrade_enabled is set to true, the type_handler_version is automatically updated by the Azure platform when a new version is available and any change in type_handler_version will be automatically ignored.

forceUpdateTag

val forceUpdateTag: Output<String>? = null

How the extension handler should be forced to update even if the extension configuration has not changed.

location

val location: Output<String>? = null

The Azure Region where the Hybrid Compute Machine Extension should exist. Changing this forces a new Hybrid Compute Machine Extension to be created.

name

val name: Output<String>? = null

The name which should be used for this Hybrid Compute Machine Extension. Changing this forces a new Hybrid Compute Machine Extension to be created.

protectedSettings

val protectedSettings: Output<String>? = null

Json formatted protected settings for the extension.

publisher

val publisher: Output<String>? = null

The name of the extension handler publisher, such as Microsoft.Azure.Monitor. Changing this forces a new Hybrid Compute Machine Extension to be created.

settings

val settings: Output<String>? = null

Json formatted public settings for the extension.

tags

val tags: Output<Map<String, String>>? = null

A mapping of tags which should be assigned to the Hybrid Compute Machine Extension.

type

val type: Output<String>? = null

Specifies the type of the extension. For example CustomScriptExtension or AzureMonitorLinuxAgent. Changing this forces a new Hybrid Compute Machine Extension to be created.

typeHandlerVersion

val typeHandlerVersion: Output<String>? = null

Specifies the version of the script handler. NOTE: 1. When automatic_upgrade_enabled is set to false and no type_handler_version is specified, the type_handler_version change should be manually ignored by ignore_changes lifecycle block. This is because the type_handler_version is set by the Azure platform when the extension is created. 2. When automatic_upgrade_enabled is set to false and type_handler_version is specified, the provider will check whether the version prefix is aligned with user input. For example, if user specifies 1.24 in type_handler_version, 1.24.1 will be considered as no diff.