We recommend using Azure Native.
azure.monitoring.LogzSubAccount
Explore with Pulumi AI
Manages a logz Sub Account.
!> Note: Logz REST API is being deprecated by Azure and new resources cannot be created. This resource will be removed in version 4.0 of the provider.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as azure from "@pulumi/azure";
const example = new azure.core.ResourceGroup("example", {
name: "example-logz",
location: "West Europe",
});
const exampleLogzMonitor = new azure.monitoring.LogzMonitor("example", {
name: "example-monitor",
resourceGroupName: example.name,
location: example.location,
plan: {
billingCycle: "MONTHLY",
effectiveDate: "2022-06-06T00:00:00Z",
usageType: "COMMITTED",
},
user: {
email: "user@example.com",
firstName: "Example",
lastName: "User",
phoneNumber: "+12313803556",
},
});
const exampleLogzSubAccount = new azure.monitoring.LogzSubAccount("example", {
name: "example-subaccount",
logzMonitorId: exampleLogzMonitor.id,
user: {
email: exampleLogzMonitor.user.apply(user => user.email),
firstName: exampleLogzMonitor.user.apply(user => user.firstName),
lastName: exampleLogzMonitor.user.apply(user => user.lastName),
phoneNumber: exampleLogzMonitor.user.apply(user => user.phoneNumber),
},
});
import pulumi
import pulumi_azure as azure
example = azure.core.ResourceGroup("example",
name="example-logz",
location="West Europe")
example_logz_monitor = azure.monitoring.LogzMonitor("example",
name="example-monitor",
resource_group_name=example.name,
location=example.location,
plan=azure.monitoring.LogzMonitorPlanArgs(
billing_cycle="MONTHLY",
effective_date="2022-06-06T00:00:00Z",
usage_type="COMMITTED",
),
user=azure.monitoring.LogzMonitorUserArgs(
email="user@example.com",
first_name="Example",
last_name="User",
phone_number="+12313803556",
))
example_logz_sub_account = azure.monitoring.LogzSubAccount("example",
name="example-subaccount",
logz_monitor_id=example_logz_monitor.id,
user=azure.monitoring.LogzSubAccountUserArgs(
email=example_logz_monitor.user.email,
first_name=example_logz_monitor.user.first_name,
last_name=example_logz_monitor.user.last_name,
phone_number=example_logz_monitor.user.phone_number,
))
package main
import (
"github.com/pulumi/pulumi-azure/sdk/v5/go/azure/core"
"github.com/pulumi/pulumi-azure/sdk/v5/go/azure/monitoring"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
example, err := core.NewResourceGroup(ctx, "example", &core.ResourceGroupArgs{
Name: pulumi.String("example-logz"),
Location: pulumi.String("West Europe"),
})
if err != nil {
return err
}
exampleLogzMonitor, err := monitoring.NewLogzMonitor(ctx, "example", &monitoring.LogzMonitorArgs{
Name: pulumi.String("example-monitor"),
ResourceGroupName: example.Name,
Location: example.Location,
Plan: &monitoring.LogzMonitorPlanArgs{
BillingCycle: pulumi.String("MONTHLY"),
EffectiveDate: pulumi.String("2022-06-06T00:00:00Z"),
UsageType: pulumi.String("COMMITTED"),
},
User: &monitoring.LogzMonitorUserArgs{
Email: pulumi.String("user@example.com"),
FirstName: pulumi.String("Example"),
LastName: pulumi.String("User"),
PhoneNumber: pulumi.String("+12313803556"),
},
})
if err != nil {
return err
}
_, err = monitoring.NewLogzSubAccount(ctx, "example", &monitoring.LogzSubAccountArgs{
Name: pulumi.String("example-subaccount"),
LogzMonitorId: exampleLogzMonitor.ID(),
User: &monitoring.LogzSubAccountUserArgs{
Email: exampleLogzMonitor.User.ApplyT(func(user monitoring.LogzMonitorUser) (*string, error) {
return &user.Email, nil
}).(pulumi.StringPtrOutput),
FirstName: exampleLogzMonitor.User.ApplyT(func(user monitoring.LogzMonitorUser) (*string, error) {
return &user.FirstName, nil
}).(pulumi.StringPtrOutput),
LastName: exampleLogzMonitor.User.ApplyT(func(user monitoring.LogzMonitorUser) (*string, error) {
return &user.LastName, nil
}).(pulumi.StringPtrOutput),
PhoneNumber: exampleLogzMonitor.User.ApplyT(func(user monitoring.LogzMonitorUser) (*string, error) {
return &user.PhoneNumber, nil
}).(pulumi.StringPtrOutput),
},
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Azure = Pulumi.Azure;
return await Deployment.RunAsync(() =>
{
var example = new Azure.Core.ResourceGroup("example", new()
{
Name = "example-logz",
Location = "West Europe",
});
var exampleLogzMonitor = new Azure.Monitoring.LogzMonitor("example", new()
{
Name = "example-monitor",
ResourceGroupName = example.Name,
Location = example.Location,
Plan = new Azure.Monitoring.Inputs.LogzMonitorPlanArgs
{
BillingCycle = "MONTHLY",
EffectiveDate = "2022-06-06T00:00:00Z",
UsageType = "COMMITTED",
},
User = new Azure.Monitoring.Inputs.LogzMonitorUserArgs
{
Email = "user@example.com",
FirstName = "Example",
LastName = "User",
PhoneNumber = "+12313803556",
},
});
var exampleLogzSubAccount = new Azure.Monitoring.LogzSubAccount("example", new()
{
Name = "example-subaccount",
LogzMonitorId = exampleLogzMonitor.Id,
User = new Azure.Monitoring.Inputs.LogzSubAccountUserArgs
{
Email = exampleLogzMonitor.User.Apply(user => user.Email),
FirstName = exampleLogzMonitor.User.Apply(user => user.FirstName),
LastName = exampleLogzMonitor.User.Apply(user => user.LastName),
PhoneNumber = exampleLogzMonitor.User.Apply(user => user.PhoneNumber),
},
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.azure.core.ResourceGroup;
import com.pulumi.azure.core.ResourceGroupArgs;
import com.pulumi.azure.monitoring.LogzMonitor;
import com.pulumi.azure.monitoring.LogzMonitorArgs;
import com.pulumi.azure.monitoring.inputs.LogzMonitorPlanArgs;
import com.pulumi.azure.monitoring.inputs.LogzMonitorUserArgs;
import com.pulumi.azure.monitoring.LogzSubAccount;
import com.pulumi.azure.monitoring.LogzSubAccountArgs;
import com.pulumi.azure.monitoring.inputs.LogzSubAccountUserArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
var example = new ResourceGroup("example", ResourceGroupArgs.builder()
.name("example-logz")
.location("West Europe")
.build());
var exampleLogzMonitor = new LogzMonitor("exampleLogzMonitor", LogzMonitorArgs.builder()
.name("example-monitor")
.resourceGroupName(example.name())
.location(example.location())
.plan(LogzMonitorPlanArgs.builder()
.billingCycle("MONTHLY")
.effectiveDate("2022-06-06T00:00:00Z")
.usageType("COMMITTED")
.build())
.user(LogzMonitorUserArgs.builder()
.email("user@example.com")
.firstName("Example")
.lastName("User")
.phoneNumber("+12313803556")
.build())
.build());
var exampleLogzSubAccount = new LogzSubAccount("exampleLogzSubAccount", LogzSubAccountArgs.builder()
.name("example-subaccount")
.logzMonitorId(exampleLogzMonitor.id())
.user(LogzSubAccountUserArgs.builder()
.email(exampleLogzMonitor.user().applyValue(user -> user.email()))
.firstName(exampleLogzMonitor.user().applyValue(user -> user.firstName()))
.lastName(exampleLogzMonitor.user().applyValue(user -> user.lastName()))
.phoneNumber(exampleLogzMonitor.user().applyValue(user -> user.phoneNumber()))
.build())
.build());
}
}
resources:
example:
type: azure:core:ResourceGroup
properties:
name: example-logz
location: West Europe
exampleLogzMonitor:
type: azure:monitoring:LogzMonitor
name: example
properties:
name: example-monitor
resourceGroupName: ${example.name}
location: ${example.location}
plan:
billingCycle: MONTHLY
effectiveDate: 2022-06-06T00:00:00Z
usageType: COMMITTED
user:
email: user@example.com
firstName: Example
lastName: User
phoneNumber: '+12313803556'
exampleLogzSubAccount:
type: azure:monitoring:LogzSubAccount
name: example
properties:
name: example-subaccount
logzMonitorId: ${exampleLogzMonitor.id}
user:
email: ${exampleLogzMonitor.user.email}
firstName: ${exampleLogzMonitor.user.firstName}
lastName: ${exampleLogzMonitor.user.lastName}
phoneNumber: ${exampleLogzMonitor.user.phoneNumber}
Create LogzSubAccount Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new LogzSubAccount(name: string, args: LogzSubAccountArgs, opts?: CustomResourceOptions);
@overload
def LogzSubAccount(resource_name: str,
args: LogzSubAccountArgs,
opts: Optional[ResourceOptions] = None)
@overload
def LogzSubAccount(resource_name: str,
opts: Optional[ResourceOptions] = None,
logz_monitor_id: Optional[str] = None,
user: Optional[LogzSubAccountUserArgs] = None,
enabled: Optional[bool] = None,
name: Optional[str] = None,
tags: Optional[Mapping[str, str]] = None)
func NewLogzSubAccount(ctx *Context, name string, args LogzSubAccountArgs, opts ...ResourceOption) (*LogzSubAccount, error)
public LogzSubAccount(string name, LogzSubAccountArgs args, CustomResourceOptions? opts = null)
public LogzSubAccount(String name, LogzSubAccountArgs args)
public LogzSubAccount(String name, LogzSubAccountArgs args, CustomResourceOptions options)
type: azure:monitoring:LogzSubAccount
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 LogzSubAccountArgs
- 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 LogzSubAccountArgs
- 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 LogzSubAccountArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args LogzSubAccountArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args LogzSubAccountArgs
- 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 logzSubAccountResource = new Azure.Monitoring.LogzSubAccount("logzSubAccountResource", new()
{
LogzMonitorId = "string",
User = new Azure.Monitoring.Inputs.LogzSubAccountUserArgs
{
Email = "string",
FirstName = "string",
LastName = "string",
PhoneNumber = "string",
},
Enabled = false,
Name = "string",
Tags =
{
{ "string", "string" },
},
});
example, err := monitoring.NewLogzSubAccount(ctx, "logzSubAccountResource", &monitoring.LogzSubAccountArgs{
LogzMonitorId: pulumi.String("string"),
User: &monitoring.LogzSubAccountUserArgs{
Email: pulumi.String("string"),
FirstName: pulumi.String("string"),
LastName: pulumi.String("string"),
PhoneNumber: pulumi.String("string"),
},
Enabled: pulumi.Bool(false),
Name: pulumi.String("string"),
Tags: pulumi.StringMap{
"string": pulumi.String("string"),
},
})
var logzSubAccountResource = new LogzSubAccount("logzSubAccountResource", LogzSubAccountArgs.builder()
.logzMonitorId("string")
.user(LogzSubAccountUserArgs.builder()
.email("string")
.firstName("string")
.lastName("string")
.phoneNumber("string")
.build())
.enabled(false)
.name("string")
.tags(Map.of("string", "string"))
.build());
logz_sub_account_resource = azure.monitoring.LogzSubAccount("logzSubAccountResource",
logz_monitor_id="string",
user=azure.monitoring.LogzSubAccountUserArgs(
email="string",
first_name="string",
last_name="string",
phone_number="string",
),
enabled=False,
name="string",
tags={
"string": "string",
})
const logzSubAccountResource = new azure.monitoring.LogzSubAccount("logzSubAccountResource", {
logzMonitorId: "string",
user: {
email: "string",
firstName: "string",
lastName: "string",
phoneNumber: "string",
},
enabled: false,
name: "string",
tags: {
string: "string",
},
});
type: azure:monitoring:LogzSubAccount
properties:
enabled: false
logzMonitorId: string
name: string
tags:
string: string
user:
email: string
firstName: string
lastName: string
phoneNumber: string
LogzSubAccount Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
The LogzSubAccount resource accepts the following input properties:
- Logz
Monitor stringId - The ID of the Logz Monitor. Changing this forces a new logz Sub Account to be created.
- User
Logz
Sub Account User - A
user
block as defined below. Changing this forces a new resource to be created. - Enabled bool
- Whether the resource monitoring is enabled? Defaults to
true
. - Name string
- The name which should be used for this logz Sub Account. Possible values must be between 1 and 32 characters in length and may contain only letters, numbers, hyphens and underscores. Changing this forces a new logz Sub Account to be created.
- Dictionary<string, string>
- A mapping of tags which should be assigned to the logz Sub Account.
- Logz
Monitor stringId - The ID of the Logz Monitor. Changing this forces a new logz Sub Account to be created.
- User
Logz
Sub Account User Args - A
user
block as defined below. Changing this forces a new resource to be created. - Enabled bool
- Whether the resource monitoring is enabled? Defaults to
true
. - Name string
- The name which should be used for this logz Sub Account. Possible values must be between 1 and 32 characters in length and may contain only letters, numbers, hyphens and underscores. Changing this forces a new logz Sub Account to be created.
- map[string]string
- A mapping of tags which should be assigned to the logz Sub Account.
- logz
Monitor StringId - The ID of the Logz Monitor. Changing this forces a new logz Sub Account to be created.
- user
Logz
Sub Account User - A
user
block as defined below. Changing this forces a new resource to be created. - enabled Boolean
- Whether the resource monitoring is enabled? Defaults to
true
. - name String
- The name which should be used for this logz Sub Account. Possible values must be between 1 and 32 characters in length and may contain only letters, numbers, hyphens and underscores. Changing this forces a new logz Sub Account to be created.
- Map<String,String>
- A mapping of tags which should be assigned to the logz Sub Account.
- logz
Monitor stringId - The ID of the Logz Monitor. Changing this forces a new logz Sub Account to be created.
- user
Logz
Sub Account User - A
user
block as defined below. Changing this forces a new resource to be created. - enabled boolean
- Whether the resource monitoring is enabled? Defaults to
true
. - name string
- The name which should be used for this logz Sub Account. Possible values must be between 1 and 32 characters in length and may contain only letters, numbers, hyphens and underscores. Changing this forces a new logz Sub Account to be created.
- {[key: string]: string}
- A mapping of tags which should be assigned to the logz Sub Account.
- logz_
monitor_ strid - The ID of the Logz Monitor. Changing this forces a new logz Sub Account to be created.
- user
Logz
Sub Account User Args - A
user
block as defined below. Changing this forces a new resource to be created. - enabled bool
- Whether the resource monitoring is enabled? Defaults to
true
. - name str
- The name which should be used for this logz Sub Account. Possible values must be between 1 and 32 characters in length and may contain only letters, numbers, hyphens and underscores. Changing this forces a new logz Sub Account to be created.
- Mapping[str, str]
- A mapping of tags which should be assigned to the logz Sub Account.
- logz
Monitor StringId - The ID of the Logz Monitor. Changing this forces a new logz Sub Account to be created.
- user Property Map
- A
user
block as defined below. Changing this forces a new resource to be created. - enabled Boolean
- Whether the resource monitoring is enabled? Defaults to
true
. - name String
- The name which should be used for this logz Sub Account. Possible values must be between 1 and 32 characters in length and may contain only letters, numbers, hyphens and underscores. Changing this forces a new logz Sub Account to be created.
- Map<String>
- A mapping of tags which should be assigned to the logz Sub Account.
Outputs
All input properties are implicitly available as output properties. Additionally, the LogzSubAccount resource produces the following output properties:
- Id string
- The provider-assigned unique ID for this managed resource.
- Id string
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
- id string
- The provider-assigned unique ID for this managed resource.
- id str
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
Look up Existing LogzSubAccount Resource
Get an existing LogzSubAccount 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?: LogzSubAccountState, opts?: CustomResourceOptions): LogzSubAccount
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
enabled: Optional[bool] = None,
logz_monitor_id: Optional[str] = None,
name: Optional[str] = None,
tags: Optional[Mapping[str, str]] = None,
user: Optional[LogzSubAccountUserArgs] = None) -> LogzSubAccount
func GetLogzSubAccount(ctx *Context, name string, id IDInput, state *LogzSubAccountState, opts ...ResourceOption) (*LogzSubAccount, error)
public static LogzSubAccount Get(string name, Input<string> id, LogzSubAccountState? state, CustomResourceOptions? opts = null)
public static LogzSubAccount get(String name, Output<String> id, LogzSubAccountState state, CustomResourceOptions options)
Resource lookup is not supported in YAML
- 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.
- Enabled bool
- Whether the resource monitoring is enabled? Defaults to
true
. - Logz
Monitor stringId - The ID of the Logz Monitor. Changing this forces a new logz Sub Account to be created.
- Name string
- The name which should be used for this logz Sub Account. Possible values must be between 1 and 32 characters in length and may contain only letters, numbers, hyphens and underscores. Changing this forces a new logz Sub Account to be created.
- Dictionary<string, string>
- A mapping of tags which should be assigned to the logz Sub Account.
- User
Logz
Sub Account User - A
user
block as defined below. Changing this forces a new resource to be created.
- Enabled bool
- Whether the resource monitoring is enabled? Defaults to
true
. - Logz
Monitor stringId - The ID of the Logz Monitor. Changing this forces a new logz Sub Account to be created.
- Name string
- The name which should be used for this logz Sub Account. Possible values must be between 1 and 32 characters in length and may contain only letters, numbers, hyphens and underscores. Changing this forces a new logz Sub Account to be created.
- map[string]string
- A mapping of tags which should be assigned to the logz Sub Account.
- User
Logz
Sub Account User Args - A
user
block as defined below. Changing this forces a new resource to be created.
- enabled Boolean
- Whether the resource monitoring is enabled? Defaults to
true
. - logz
Monitor StringId - The ID of the Logz Monitor. Changing this forces a new logz Sub Account to be created.
- name String
- The name which should be used for this logz Sub Account. Possible values must be between 1 and 32 characters in length and may contain only letters, numbers, hyphens and underscores. Changing this forces a new logz Sub Account to be created.
- Map<String,String>
- A mapping of tags which should be assigned to the logz Sub Account.
- user
Logz
Sub Account User - A
user
block as defined below. Changing this forces a new resource to be created.
- enabled boolean
- Whether the resource monitoring is enabled? Defaults to
true
. - logz
Monitor stringId - The ID of the Logz Monitor. Changing this forces a new logz Sub Account to be created.
- name string
- The name which should be used for this logz Sub Account. Possible values must be between 1 and 32 characters in length and may contain only letters, numbers, hyphens and underscores. Changing this forces a new logz Sub Account to be created.
- {[key: string]: string}
- A mapping of tags which should be assigned to the logz Sub Account.
- user
Logz
Sub Account User - A
user
block as defined below. Changing this forces a new resource to be created.
- enabled bool
- Whether the resource monitoring is enabled? Defaults to
true
. - logz_
monitor_ strid - The ID of the Logz Monitor. Changing this forces a new logz Sub Account to be created.
- name str
- The name which should be used for this logz Sub Account. Possible values must be between 1 and 32 characters in length and may contain only letters, numbers, hyphens and underscores. Changing this forces a new logz Sub Account to be created.
- Mapping[str, str]
- A mapping of tags which should be assigned to the logz Sub Account.
- user
Logz
Sub Account User Args - A
user
block as defined below. Changing this forces a new resource to be created.
- enabled Boolean
- Whether the resource monitoring is enabled? Defaults to
true
. - logz
Monitor StringId - The ID of the Logz Monitor. Changing this forces a new logz Sub Account to be created.
- name String
- The name which should be used for this logz Sub Account. Possible values must be between 1 and 32 characters in length and may contain only letters, numbers, hyphens and underscores. Changing this forces a new logz Sub Account to be created.
- Map<String>
- A mapping of tags which should be assigned to the logz Sub Account.
- user Property Map
- A
user
block as defined below. Changing this forces a new resource to be created.
Supporting Types
LogzSubAccountUser, LogzSubAccountUserArgs
- Email string
Email of the user used by Logz for contacting them if needed. A valid email address consists of an email prefix and an email domain. The prefix and domain may contain only letters, numbers, underscores, periods and dashes. Changing this forces a new logz Sub Account to be created.
NOTE If you use the Azure CLI to authenticate to Azure, the Email of your Azure account needs to be granted the admin permission in your Logz.io account. Otherwise, you may not be able to delete this resource. There is no such limitation for the Service Principal authentication.
- First
Name string - First Name of the user. Possible values must be between 1 and 50 characters in length. Changing this forces a new logz Sub Account to be created.
- Last
Name string - Last Name of the user. Possible values must be between 1 and 50 characters in length. Changing this forces a new logz Sub Account to be created.
- Phone
Number string - Phone number of the user used by Logz for contacting them if needed. Possible values must be between 1 and 40 characters in length. Changing this forces a new logz Sub Account to be created.
- Email string
Email of the user used by Logz for contacting them if needed. A valid email address consists of an email prefix and an email domain. The prefix and domain may contain only letters, numbers, underscores, periods and dashes. Changing this forces a new logz Sub Account to be created.
NOTE If you use the Azure CLI to authenticate to Azure, the Email of your Azure account needs to be granted the admin permission in your Logz.io account. Otherwise, you may not be able to delete this resource. There is no such limitation for the Service Principal authentication.
- First
Name string - First Name of the user. Possible values must be between 1 and 50 characters in length. Changing this forces a new logz Sub Account to be created.
- Last
Name string - Last Name of the user. Possible values must be between 1 and 50 characters in length. Changing this forces a new logz Sub Account to be created.
- Phone
Number string - Phone number of the user used by Logz for contacting them if needed. Possible values must be between 1 and 40 characters in length. Changing this forces a new logz Sub Account to be created.
- email String
Email of the user used by Logz for contacting them if needed. A valid email address consists of an email prefix and an email domain. The prefix and domain may contain only letters, numbers, underscores, periods and dashes. Changing this forces a new logz Sub Account to be created.
NOTE If you use the Azure CLI to authenticate to Azure, the Email of your Azure account needs to be granted the admin permission in your Logz.io account. Otherwise, you may not be able to delete this resource. There is no such limitation for the Service Principal authentication.
- first
Name String - First Name of the user. Possible values must be between 1 and 50 characters in length. Changing this forces a new logz Sub Account to be created.
- last
Name String - Last Name of the user. Possible values must be between 1 and 50 characters in length. Changing this forces a new logz Sub Account to be created.
- phone
Number String - Phone number of the user used by Logz for contacting them if needed. Possible values must be between 1 and 40 characters in length. Changing this forces a new logz Sub Account to be created.
- email string
Email of the user used by Logz for contacting them if needed. A valid email address consists of an email prefix and an email domain. The prefix and domain may contain only letters, numbers, underscores, periods and dashes. Changing this forces a new logz Sub Account to be created.
NOTE If you use the Azure CLI to authenticate to Azure, the Email of your Azure account needs to be granted the admin permission in your Logz.io account. Otherwise, you may not be able to delete this resource. There is no such limitation for the Service Principal authentication.
- first
Name string - First Name of the user. Possible values must be between 1 and 50 characters in length. Changing this forces a new logz Sub Account to be created.
- last
Name string - Last Name of the user. Possible values must be between 1 and 50 characters in length. Changing this forces a new logz Sub Account to be created.
- phone
Number string - Phone number of the user used by Logz for contacting them if needed. Possible values must be between 1 and 40 characters in length. Changing this forces a new logz Sub Account to be created.
- email str
Email of the user used by Logz for contacting them if needed. A valid email address consists of an email prefix and an email domain. The prefix and domain may contain only letters, numbers, underscores, periods and dashes. Changing this forces a new logz Sub Account to be created.
NOTE If you use the Azure CLI to authenticate to Azure, the Email of your Azure account needs to be granted the admin permission in your Logz.io account. Otherwise, you may not be able to delete this resource. There is no such limitation for the Service Principal authentication.
- first_
name str - First Name of the user. Possible values must be between 1 and 50 characters in length. Changing this forces a new logz Sub Account to be created.
- last_
name str - Last Name of the user. Possible values must be between 1 and 50 characters in length. Changing this forces a new logz Sub Account to be created.
- phone_
number str - Phone number of the user used by Logz for contacting them if needed. Possible values must be between 1 and 40 characters in length. Changing this forces a new logz Sub Account to be created.
- email String
Email of the user used by Logz for contacting them if needed. A valid email address consists of an email prefix and an email domain. The prefix and domain may contain only letters, numbers, underscores, periods and dashes. Changing this forces a new logz Sub Account to be created.
NOTE If you use the Azure CLI to authenticate to Azure, the Email of your Azure account needs to be granted the admin permission in your Logz.io account. Otherwise, you may not be able to delete this resource. There is no such limitation for the Service Principal authentication.
- first
Name String - First Name of the user. Possible values must be between 1 and 50 characters in length. Changing this forces a new logz Sub Account to be created.
- last
Name String - Last Name of the user. Possible values must be between 1 and 50 characters in length. Changing this forces a new logz Sub Account to be created.
- phone
Number String - Phone number of the user used by Logz for contacting them if needed. Possible values must be between 1 and 40 characters in length. Changing this forces a new logz Sub Account to be created.
Import
logz SubAccounts can be imported using the resource id
, e.g.
$ pulumi import azure:monitoring/logzSubAccount:LogzSubAccount example /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/group1/providers/Microsoft.Logz/monitors/monitor1/accounts/subAccount1
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- Azure Classic pulumi/pulumi-azure
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
azurerm
Terraform Provider.