Dynatrace v0.10.0 published on Friday, Jun 7, 2024 by Pulumiverse
dynatrace.OwnershipTeams
Explore with Pulumi AI
Create OwnershipTeams Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new OwnershipTeams(name: string, args: OwnershipTeamsArgs, opts?: CustomResourceOptions);
@overload
def OwnershipTeams(resource_name: str,
args: OwnershipTeamsArgs,
opts: Optional[ResourceOptions] = None)
@overload
def OwnershipTeams(resource_name: str,
opts: Optional[ResourceOptions] = None,
identifier: Optional[str] = None,
responsibilities: Optional[OwnershipTeamsResponsibilitiesArgs] = None,
additional_information: Optional[OwnershipTeamsAdditionalInformationArgs] = None,
contact_details: Optional[OwnershipTeamsContactDetailsArgs] = None,
description: Optional[str] = None,
external_id: Optional[str] = None,
links: Optional[OwnershipTeamsLinksArgs] = None,
name: Optional[str] = None,
supplementary_identifiers: Optional[OwnershipTeamsSupplementaryIdentifiersArgs] = None)
func NewOwnershipTeams(ctx *Context, name string, args OwnershipTeamsArgs, opts ...ResourceOption) (*OwnershipTeams, error)
public OwnershipTeams(string name, OwnershipTeamsArgs args, CustomResourceOptions? opts = null)
public OwnershipTeams(String name, OwnershipTeamsArgs args)
public OwnershipTeams(String name, OwnershipTeamsArgs args, CustomResourceOptions options)
type: dynatrace:OwnershipTeams
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 OwnershipTeamsArgs
- 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 OwnershipTeamsArgs
- 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 OwnershipTeamsArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args OwnershipTeamsArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args OwnershipTeamsArgs
- 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 ownershipTeamsResource = new Dynatrace.OwnershipTeams("ownershipTeamsResource", new()
{
Identifier = "string",
Responsibilities = new Dynatrace.Inputs.OwnershipTeamsResponsibilitiesArgs
{
Development = false,
Infrastructure = false,
LineOfBusiness = false,
Operations = false,
Security = false,
},
AdditionalInformation = new Dynatrace.Inputs.OwnershipTeamsAdditionalInformationArgs
{
AdditionalInformations = new[]
{
new Dynatrace.Inputs.OwnershipTeamsAdditionalInformationAdditionalInformationArgs
{
Key = "string",
Value = "string",
Url = "string",
},
},
},
ContactDetails = new Dynatrace.Inputs.OwnershipTeamsContactDetailsArgs
{
ContactDetails = new[]
{
new Dynatrace.Inputs.OwnershipTeamsContactDetailsContactDetailArgs
{
IntegrationType = "string",
Email = "string",
Jira = new Dynatrace.Inputs.OwnershipTeamsContactDetailsContactDetailJiraArgs
{
DefaultAssignee = "string",
Project = "string",
},
MsTeams = "string",
SlackChannel = "string",
Url = "string",
},
},
},
Description = "string",
ExternalId = "string",
Links = new Dynatrace.Inputs.OwnershipTeamsLinksArgs
{
Links = new[]
{
new Dynatrace.Inputs.OwnershipTeamsLinksLinkArgs
{
LinkType = "string",
Url = "string",
},
},
},
Name = "string",
SupplementaryIdentifiers = new Dynatrace.Inputs.OwnershipTeamsSupplementaryIdentifiersArgs
{
SupplementaryIdentifiers = new[]
{
new Dynatrace.Inputs.OwnershipTeamsSupplementaryIdentifiersSupplementaryIdentifierArgs
{
SupplementaryIdentifier = "string",
},
},
},
});
example, err := dynatrace.NewOwnershipTeams(ctx, "ownershipTeamsResource", &dynatrace.OwnershipTeamsArgs{
Identifier: pulumi.String("string"),
Responsibilities: &dynatrace.OwnershipTeamsResponsibilitiesArgs{
Development: pulumi.Bool(false),
Infrastructure: pulumi.Bool(false),
LineOfBusiness: pulumi.Bool(false),
Operations: pulumi.Bool(false),
Security: pulumi.Bool(false),
},
AdditionalInformation: &dynatrace.OwnershipTeamsAdditionalInformationArgs{
AdditionalInformations: dynatrace.OwnershipTeamsAdditionalInformationAdditionalInformationArray{
&dynatrace.OwnershipTeamsAdditionalInformationAdditionalInformationArgs{
Key: pulumi.String("string"),
Value: pulumi.String("string"),
Url: pulumi.String("string"),
},
},
},
ContactDetails: &dynatrace.OwnershipTeamsContactDetailsArgs{
ContactDetails: dynatrace.OwnershipTeamsContactDetailsContactDetailArray{
&dynatrace.OwnershipTeamsContactDetailsContactDetailArgs{
IntegrationType: pulumi.String("string"),
Email: pulumi.String("string"),
Jira: &dynatrace.OwnershipTeamsContactDetailsContactDetailJiraArgs{
DefaultAssignee: pulumi.String("string"),
Project: pulumi.String("string"),
},
MsTeams: pulumi.String("string"),
SlackChannel: pulumi.String("string"),
Url: pulumi.String("string"),
},
},
},
Description: pulumi.String("string"),
ExternalId: pulumi.String("string"),
Links: &dynatrace.OwnershipTeamsLinksArgs{
Links: dynatrace.OwnershipTeamsLinksLinkArray{
&dynatrace.OwnershipTeamsLinksLinkArgs{
LinkType: pulumi.String("string"),
Url: pulumi.String("string"),
},
},
},
Name: pulumi.String("string"),
SupplementaryIdentifiers: &dynatrace.OwnershipTeamsSupplementaryIdentifiersArgs{
SupplementaryIdentifiers: dynatrace.OwnershipTeamsSupplementaryIdentifiersSupplementaryIdentifierArray{
&dynatrace.OwnershipTeamsSupplementaryIdentifiersSupplementaryIdentifierArgs{
SupplementaryIdentifier: pulumi.String("string"),
},
},
},
})
var ownershipTeamsResource = new OwnershipTeams("ownershipTeamsResource", OwnershipTeamsArgs.builder()
.identifier("string")
.responsibilities(OwnershipTeamsResponsibilitiesArgs.builder()
.development(false)
.infrastructure(false)
.lineOfBusiness(false)
.operations(false)
.security(false)
.build())
.additionalInformation(OwnershipTeamsAdditionalInformationArgs.builder()
.additionalInformations(OwnershipTeamsAdditionalInformationAdditionalInformationArgs.builder()
.key("string")
.value("string")
.url("string")
.build())
.build())
.contactDetails(OwnershipTeamsContactDetailsArgs.builder()
.contactDetails(OwnershipTeamsContactDetailsContactDetailArgs.builder()
.integrationType("string")
.email("string")
.jira(OwnershipTeamsContactDetailsContactDetailJiraArgs.builder()
.defaultAssignee("string")
.project("string")
.build())
.msTeams("string")
.slackChannel("string")
.url("string")
.build())
.build())
.description("string")
.externalId("string")
.links(OwnershipTeamsLinksArgs.builder()
.links(OwnershipTeamsLinksLinkArgs.builder()
.linkType("string")
.url("string")
.build())
.build())
.name("string")
.supplementaryIdentifiers(OwnershipTeamsSupplementaryIdentifiersArgs.builder()
.supplementaryIdentifiers(OwnershipTeamsSupplementaryIdentifiersSupplementaryIdentifierArgs.builder()
.supplementaryIdentifier("string")
.build())
.build())
.build());
ownership_teams_resource = dynatrace.OwnershipTeams("ownershipTeamsResource",
identifier="string",
responsibilities=dynatrace.OwnershipTeamsResponsibilitiesArgs(
development=False,
infrastructure=False,
line_of_business=False,
operations=False,
security=False,
),
additional_information=dynatrace.OwnershipTeamsAdditionalInformationArgs(
additional_informations=[dynatrace.OwnershipTeamsAdditionalInformationAdditionalInformationArgs(
key="string",
value="string",
url="string",
)],
),
contact_details=dynatrace.OwnershipTeamsContactDetailsArgs(
contact_details=[dynatrace.OwnershipTeamsContactDetailsContactDetailArgs(
integration_type="string",
email="string",
jira=dynatrace.OwnershipTeamsContactDetailsContactDetailJiraArgs(
default_assignee="string",
project="string",
),
ms_teams="string",
slack_channel="string",
url="string",
)],
),
description="string",
external_id="string",
links=dynatrace.OwnershipTeamsLinksArgs(
links=[dynatrace.OwnershipTeamsLinksLinkArgs(
link_type="string",
url="string",
)],
),
name="string",
supplementary_identifiers=dynatrace.OwnershipTeamsSupplementaryIdentifiersArgs(
supplementary_identifiers=[dynatrace.OwnershipTeamsSupplementaryIdentifiersSupplementaryIdentifierArgs(
supplementary_identifier="string",
)],
))
const ownershipTeamsResource = new dynatrace.OwnershipTeams("ownershipTeamsResource", {
identifier: "string",
responsibilities: {
development: false,
infrastructure: false,
lineOfBusiness: false,
operations: false,
security: false,
},
additionalInformation: {
additionalInformations: [{
key: "string",
value: "string",
url: "string",
}],
},
contactDetails: {
contactDetails: [{
integrationType: "string",
email: "string",
jira: {
defaultAssignee: "string",
project: "string",
},
msTeams: "string",
slackChannel: "string",
url: "string",
}],
},
description: "string",
externalId: "string",
links: {
links: [{
linkType: "string",
url: "string",
}],
},
name: "string",
supplementaryIdentifiers: {
supplementaryIdentifiers: [{
supplementaryIdentifier: "string",
}],
},
});
type: dynatrace:OwnershipTeams
properties:
additionalInformation:
additionalInformations:
- key: string
url: string
value: string
contactDetails:
contactDetails:
- email: string
integrationType: string
jira:
defaultAssignee: string
project: string
msTeams: string
slackChannel: string
url: string
description: string
externalId: string
identifier: string
links:
links:
- linkType: string
url: string
name: string
responsibilities:
development: false
infrastructure: false
lineOfBusiness: false
operations: false
security: false
supplementaryIdentifiers:
supplementaryIdentifiers:
- supplementaryIdentifier: string
OwnershipTeams 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 OwnershipTeams resource accepts the following input properties:
- Identifier string
- The team identifier is used to reference the team from any entity in Dynatrace. If you are using Kubernetes labels, keep in mind the 63 character limit that they enforce.
- Responsibilities
Pulumiverse.
Dynatrace. Inputs. Ownership Teams Responsibilities - Turn on all responsibility assignments that apply to this team.
- Additional
Information Pulumiverse.Dynatrace. Inputs. Ownership Teams Additional Information - Define key/value pairs that further describe this team — for example, cost center, solution type, or business unit assignments.
- Contact
Details Pulumiverse.Dynatrace. Inputs. Ownership Teams Contact Details - Define options for messaging integration or other means of contacting this team.
- Description string
- Description
- External
Id string - This field should only be used for the automation purpose when importing team information.
- Links
Pulumiverse.
Dynatrace. Inputs. Ownership Teams Links - Include links to online resources where information relevant to this team’s responsibilities can be found.
- Name string
- Team name
- Supplementary
Identifiers Pulumiverse.Dynatrace. Inputs. Ownership Teams Supplementary Identifiers - The supplementary team identifiers can be optionally used in addition to the main team identifier to reference this team from any entity in Dynatrace. Up to 3 supplementary identifiers are supported.
- Identifier string
- The team identifier is used to reference the team from any entity in Dynatrace. If you are using Kubernetes labels, keep in mind the 63 character limit that they enforce.
- Responsibilities
Ownership
Teams Responsibilities Args - Turn on all responsibility assignments that apply to this team.
- Additional
Information OwnershipTeams Additional Information Args - Define key/value pairs that further describe this team — for example, cost center, solution type, or business unit assignments.
- Contact
Details OwnershipTeams Contact Details Args - Define options for messaging integration or other means of contacting this team.
- Description string
- Description
- External
Id string - This field should only be used for the automation purpose when importing team information.
- Links
Ownership
Teams Links Args - Include links to online resources where information relevant to this team’s responsibilities can be found.
- Name string
- Team name
- Supplementary
Identifiers OwnershipTeams Supplementary Identifiers Args - The supplementary team identifiers can be optionally used in addition to the main team identifier to reference this team from any entity in Dynatrace. Up to 3 supplementary identifiers are supported.
- identifier String
- The team identifier is used to reference the team from any entity in Dynatrace. If you are using Kubernetes labels, keep in mind the 63 character limit that they enforce.
- responsibilities
Ownership
Teams Responsibilities - Turn on all responsibility assignments that apply to this team.
- additional
Information OwnershipTeams Additional Information - Define key/value pairs that further describe this team — for example, cost center, solution type, or business unit assignments.
- contact
Details OwnershipTeams Contact Details - Define options for messaging integration or other means of contacting this team.
- description String
- Description
- external
Id String - This field should only be used for the automation purpose when importing team information.
- links
Ownership
Teams Links - Include links to online resources where information relevant to this team’s responsibilities can be found.
- name String
- Team name
- supplementary
Identifiers OwnershipTeams Supplementary Identifiers - The supplementary team identifiers can be optionally used in addition to the main team identifier to reference this team from any entity in Dynatrace. Up to 3 supplementary identifiers are supported.
- identifier string
- The team identifier is used to reference the team from any entity in Dynatrace. If you are using Kubernetes labels, keep in mind the 63 character limit that they enforce.
- responsibilities
Ownership
Teams Responsibilities - Turn on all responsibility assignments that apply to this team.
- additional
Information OwnershipTeams Additional Information - Define key/value pairs that further describe this team — for example, cost center, solution type, or business unit assignments.
- contact
Details OwnershipTeams Contact Details - Define options for messaging integration or other means of contacting this team.
- description string
- Description
- external
Id string - This field should only be used for the automation purpose when importing team information.
- links
Ownership
Teams Links - Include links to online resources where information relevant to this team’s responsibilities can be found.
- name string
- Team name
- supplementary
Identifiers OwnershipTeams Supplementary Identifiers - The supplementary team identifiers can be optionally used in addition to the main team identifier to reference this team from any entity in Dynatrace. Up to 3 supplementary identifiers are supported.
- identifier str
- The team identifier is used to reference the team from any entity in Dynatrace. If you are using Kubernetes labels, keep in mind the 63 character limit that they enforce.
- responsibilities
Ownership
Teams Responsibilities Args - Turn on all responsibility assignments that apply to this team.
- additional_
information OwnershipTeams Additional Information Args - Define key/value pairs that further describe this team — for example, cost center, solution type, or business unit assignments.
- contact_
details OwnershipTeams Contact Details Args - Define options for messaging integration or other means of contacting this team.
- description str
- Description
- external_
id str - This field should only be used for the automation purpose when importing team information.
- links
Ownership
Teams Links Args - Include links to online resources where information relevant to this team’s responsibilities can be found.
- name str
- Team name
- supplementary_
identifiers OwnershipTeams Supplementary Identifiers Args - The supplementary team identifiers can be optionally used in addition to the main team identifier to reference this team from any entity in Dynatrace. Up to 3 supplementary identifiers are supported.
- identifier String
- The team identifier is used to reference the team from any entity in Dynatrace. If you are using Kubernetes labels, keep in mind the 63 character limit that they enforce.
- responsibilities Property Map
- Turn on all responsibility assignments that apply to this team.
- additional
Information Property Map - Define key/value pairs that further describe this team — for example, cost center, solution type, or business unit assignments.
- contact
Details Property Map - Define options for messaging integration or other means of contacting this team.
- description String
- Description
- external
Id String - This field should only be used for the automation purpose when importing team information.
- links Property Map
- Include links to online resources where information relevant to this team’s responsibilities can be found.
- name String
- Team name
- supplementary
Identifiers Property Map - The supplementary team identifiers can be optionally used in addition to the main team identifier to reference this team from any entity in Dynatrace. Up to 3 supplementary identifiers are supported.
Outputs
All input properties are implicitly available as output properties. Additionally, the OwnershipTeams 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 OwnershipTeams Resource
Get an existing OwnershipTeams 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?: OwnershipTeamsState, opts?: CustomResourceOptions): OwnershipTeams
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
additional_information: Optional[OwnershipTeamsAdditionalInformationArgs] = None,
contact_details: Optional[OwnershipTeamsContactDetailsArgs] = None,
description: Optional[str] = None,
external_id: Optional[str] = None,
identifier: Optional[str] = None,
links: Optional[OwnershipTeamsLinksArgs] = None,
name: Optional[str] = None,
responsibilities: Optional[OwnershipTeamsResponsibilitiesArgs] = None,
supplementary_identifiers: Optional[OwnershipTeamsSupplementaryIdentifiersArgs] = None) -> OwnershipTeams
func GetOwnershipTeams(ctx *Context, name string, id IDInput, state *OwnershipTeamsState, opts ...ResourceOption) (*OwnershipTeams, error)
public static OwnershipTeams Get(string name, Input<string> id, OwnershipTeamsState? state, CustomResourceOptions? opts = null)
public static OwnershipTeams get(String name, Output<String> id, OwnershipTeamsState 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.
- Additional
Information Pulumiverse.Dynatrace. Inputs. Ownership Teams Additional Information - Define key/value pairs that further describe this team — for example, cost center, solution type, or business unit assignments.
- Contact
Details Pulumiverse.Dynatrace. Inputs. Ownership Teams Contact Details - Define options for messaging integration or other means of contacting this team.
- Description string
- Description
- External
Id string - This field should only be used for the automation purpose when importing team information.
- Identifier string
- The team identifier is used to reference the team from any entity in Dynatrace. If you are using Kubernetes labels, keep in mind the 63 character limit that they enforce.
- Links
Pulumiverse.
Dynatrace. Inputs. Ownership Teams Links - Include links to online resources where information relevant to this team’s responsibilities can be found.
- Name string
- Team name
- Responsibilities
Pulumiverse.
Dynatrace. Inputs. Ownership Teams Responsibilities - Turn on all responsibility assignments that apply to this team.
- Supplementary
Identifiers Pulumiverse.Dynatrace. Inputs. Ownership Teams Supplementary Identifiers - The supplementary team identifiers can be optionally used in addition to the main team identifier to reference this team from any entity in Dynatrace. Up to 3 supplementary identifiers are supported.
- Additional
Information OwnershipTeams Additional Information Args - Define key/value pairs that further describe this team — for example, cost center, solution type, or business unit assignments.
- Contact
Details OwnershipTeams Contact Details Args - Define options for messaging integration or other means of contacting this team.
- Description string
- Description
- External
Id string - This field should only be used for the automation purpose when importing team information.
- Identifier string
- The team identifier is used to reference the team from any entity in Dynatrace. If you are using Kubernetes labels, keep in mind the 63 character limit that they enforce.
- Links
Ownership
Teams Links Args - Include links to online resources where information relevant to this team’s responsibilities can be found.
- Name string
- Team name
- Responsibilities
Ownership
Teams Responsibilities Args - Turn on all responsibility assignments that apply to this team.
- Supplementary
Identifiers OwnershipTeams Supplementary Identifiers Args - The supplementary team identifiers can be optionally used in addition to the main team identifier to reference this team from any entity in Dynatrace. Up to 3 supplementary identifiers are supported.
- additional
Information OwnershipTeams Additional Information - Define key/value pairs that further describe this team — for example, cost center, solution type, or business unit assignments.
- contact
Details OwnershipTeams Contact Details - Define options for messaging integration or other means of contacting this team.
- description String
- Description
- external
Id String - This field should only be used for the automation purpose when importing team information.
- identifier String
- The team identifier is used to reference the team from any entity in Dynatrace. If you are using Kubernetes labels, keep in mind the 63 character limit that they enforce.
- links
Ownership
Teams Links - Include links to online resources where information relevant to this team’s responsibilities can be found.
- name String
- Team name
- responsibilities
Ownership
Teams Responsibilities - Turn on all responsibility assignments that apply to this team.
- supplementary
Identifiers OwnershipTeams Supplementary Identifiers - The supplementary team identifiers can be optionally used in addition to the main team identifier to reference this team from any entity in Dynatrace. Up to 3 supplementary identifiers are supported.
- additional
Information OwnershipTeams Additional Information - Define key/value pairs that further describe this team — for example, cost center, solution type, or business unit assignments.
- contact
Details OwnershipTeams Contact Details - Define options for messaging integration or other means of contacting this team.
- description string
- Description
- external
Id string - This field should only be used for the automation purpose when importing team information.
- identifier string
- The team identifier is used to reference the team from any entity in Dynatrace. If you are using Kubernetes labels, keep in mind the 63 character limit that they enforce.
- links
Ownership
Teams Links - Include links to online resources where information relevant to this team’s responsibilities can be found.
- name string
- Team name
- responsibilities
Ownership
Teams Responsibilities - Turn on all responsibility assignments that apply to this team.
- supplementary
Identifiers OwnershipTeams Supplementary Identifiers - The supplementary team identifiers can be optionally used in addition to the main team identifier to reference this team from any entity in Dynatrace. Up to 3 supplementary identifiers are supported.
- additional_
information OwnershipTeams Additional Information Args - Define key/value pairs that further describe this team — for example, cost center, solution type, or business unit assignments.
- contact_
details OwnershipTeams Contact Details Args - Define options for messaging integration or other means of contacting this team.
- description str
- Description
- external_
id str - This field should only be used for the automation purpose when importing team information.
- identifier str
- The team identifier is used to reference the team from any entity in Dynatrace. If you are using Kubernetes labels, keep in mind the 63 character limit that they enforce.
- links
Ownership
Teams Links Args - Include links to online resources where information relevant to this team’s responsibilities can be found.
- name str
- Team name
- responsibilities
Ownership
Teams Responsibilities Args - Turn on all responsibility assignments that apply to this team.
- supplementary_
identifiers OwnershipTeams Supplementary Identifiers Args - The supplementary team identifiers can be optionally used in addition to the main team identifier to reference this team from any entity in Dynatrace. Up to 3 supplementary identifiers are supported.
- additional
Information Property Map - Define key/value pairs that further describe this team — for example, cost center, solution type, or business unit assignments.
- contact
Details Property Map - Define options for messaging integration or other means of contacting this team.
- description String
- Description
- external
Id String - This field should only be used for the automation purpose when importing team information.
- identifier String
- The team identifier is used to reference the team from any entity in Dynatrace. If you are using Kubernetes labels, keep in mind the 63 character limit that they enforce.
- links Property Map
- Include links to online resources where information relevant to this team’s responsibilities can be found.
- name String
- Team name
- responsibilities Property Map
- Turn on all responsibility assignments that apply to this team.
- supplementary
Identifiers Property Map - The supplementary team identifiers can be optionally used in addition to the main team identifier to reference this team from any entity in Dynatrace. Up to 3 supplementary identifiers are supported.
Supporting Types
OwnershipTeamsAdditionalInformation, OwnershipTeamsAdditionalInformationArgs
OwnershipTeamsAdditionalInformationAdditionalInformation, OwnershipTeamsAdditionalInformationAdditionalInformationArgs
OwnershipTeamsContactDetails, OwnershipTeamsContactDetailsArgs
OwnershipTeamsContactDetailsContactDetail, OwnershipTeamsContactDetailsContactDetailArgs
- Integration
Type string - Possible Values:
EMAIL
,JIRA
,MS_TEAMS
,SLACK
- Email string
- no documentation available
- Jira
Pulumiverse.
Dynatrace. Inputs. Ownership Teams Contact Details Contact Detail Jira - no documentation available
- Ms
Teams string - Team
- Slack
Channel string - Channel
- Url string
- no documentation available
- Integration
Type string - Possible Values:
EMAIL
,JIRA
,MS_TEAMS
,SLACK
- Email string
- no documentation available
- Jira
Ownership
Teams Contact Details Contact Detail Jira - no documentation available
- Ms
Teams string - Team
- Slack
Channel string - Channel
- Url string
- no documentation available
- integration
Type String - Possible Values:
EMAIL
,JIRA
,MS_TEAMS
,SLACK
- email String
- no documentation available
- jira
Ownership
Teams Contact Details Contact Detail Jira - no documentation available
- ms
Teams String - Team
- slack
Channel String - Channel
- url String
- no documentation available
- integration
Type string - Possible Values:
EMAIL
,JIRA
,MS_TEAMS
,SLACK
- email string
- no documentation available
- jira
Ownership
Teams Contact Details Contact Detail Jira - no documentation available
- ms
Teams string - Team
- slack
Channel string - Channel
- url string
- no documentation available
- integration_
type str - Possible Values:
EMAIL
,JIRA
,MS_TEAMS
,SLACK
- email str
- no documentation available
- jira
Ownership
Teams Contact Details Contact Detail Jira - no documentation available
- ms_
teams str - Team
- slack_
channel str - Channel
- url str
- no documentation available
- integration
Type String - Possible Values:
EMAIL
,JIRA
,MS_TEAMS
,SLACK
- email String
- no documentation available
- jira Property Map
- no documentation available
- ms
Teams String - Team
- slack
Channel String - Channel
- url String
- no documentation available
OwnershipTeamsContactDetailsContactDetailJira, OwnershipTeamsContactDetailsContactDetailJiraArgs
- Default
Assignee string - Default Assignee
- Project string
- no documentation available
- Default
Assignee string - Default Assignee
- Project string
- no documentation available
- default
Assignee String - Default Assignee
- project String
- no documentation available
- default
Assignee string - Default Assignee
- project string
- no documentation available
- default_
assignee str - Default Assignee
- project str
- no documentation available
- default
Assignee String - Default Assignee
- project String
- no documentation available
OwnershipTeamsLinks, OwnershipTeamsLinksArgs
OwnershipTeamsLinksLink, OwnershipTeamsLinksLinkArgs
OwnershipTeamsResponsibilities, OwnershipTeamsResponsibilitiesArgs
- Development bool
- Responsible for developing and maintaining high quality software. Development teams are responsible for making code changes to address performance regressions, errors, or security vulnerabilities.
- Infrastructure bool
- Responsible for the administration, management, and support of the IT infrastructure including physical servers, virtualization, and cloud. Teams with infrastructure responsibility are responsible for addressing hardware issues, resource limits, and operating system vulnerabilities.
- Line
Of boolBusiness - Responsible for ensuring that applications in development align with business needs and meet the usability requirements of users, stakeholders, customers, and external partners. Teams with line of business responsibility are responsible for understanding the customer experience and how it affects business goals.
- Operations bool
- Responsible for deploying and managing software, with a focus on high availability and performance. Teams with operations responsibilities needs to understand the impact, priority, and team responsible for addressing problems detected by Dynatrace.
- Security bool
- Responsible for the security posture of the organization. Teams with security responsibility must understand the impact, priority, and team responsible for addressing security vulnerabilities.
- Development bool
- Responsible for developing and maintaining high quality software. Development teams are responsible for making code changes to address performance regressions, errors, or security vulnerabilities.
- Infrastructure bool
- Responsible for the administration, management, and support of the IT infrastructure including physical servers, virtualization, and cloud. Teams with infrastructure responsibility are responsible for addressing hardware issues, resource limits, and operating system vulnerabilities.
- Line
Of boolBusiness - Responsible for ensuring that applications in development align with business needs and meet the usability requirements of users, stakeholders, customers, and external partners. Teams with line of business responsibility are responsible for understanding the customer experience and how it affects business goals.
- Operations bool
- Responsible for deploying and managing software, with a focus on high availability and performance. Teams with operations responsibilities needs to understand the impact, priority, and team responsible for addressing problems detected by Dynatrace.
- Security bool
- Responsible for the security posture of the organization. Teams with security responsibility must understand the impact, priority, and team responsible for addressing security vulnerabilities.
- development Boolean
- Responsible for developing and maintaining high quality software. Development teams are responsible for making code changes to address performance regressions, errors, or security vulnerabilities.
- infrastructure Boolean
- Responsible for the administration, management, and support of the IT infrastructure including physical servers, virtualization, and cloud. Teams with infrastructure responsibility are responsible for addressing hardware issues, resource limits, and operating system vulnerabilities.
- line
Of BooleanBusiness - Responsible for ensuring that applications in development align with business needs and meet the usability requirements of users, stakeholders, customers, and external partners. Teams with line of business responsibility are responsible for understanding the customer experience and how it affects business goals.
- operations Boolean
- Responsible for deploying and managing software, with a focus on high availability and performance. Teams with operations responsibilities needs to understand the impact, priority, and team responsible for addressing problems detected by Dynatrace.
- security Boolean
- Responsible for the security posture of the organization. Teams with security responsibility must understand the impact, priority, and team responsible for addressing security vulnerabilities.
- development boolean
- Responsible for developing and maintaining high quality software. Development teams are responsible for making code changes to address performance regressions, errors, or security vulnerabilities.
- infrastructure boolean
- Responsible for the administration, management, and support of the IT infrastructure including physical servers, virtualization, and cloud. Teams with infrastructure responsibility are responsible for addressing hardware issues, resource limits, and operating system vulnerabilities.
- line
Of booleanBusiness - Responsible for ensuring that applications in development align with business needs and meet the usability requirements of users, stakeholders, customers, and external partners. Teams with line of business responsibility are responsible for understanding the customer experience and how it affects business goals.
- operations boolean
- Responsible for deploying and managing software, with a focus on high availability and performance. Teams with operations responsibilities needs to understand the impact, priority, and team responsible for addressing problems detected by Dynatrace.
- security boolean
- Responsible for the security posture of the organization. Teams with security responsibility must understand the impact, priority, and team responsible for addressing security vulnerabilities.
- development bool
- Responsible for developing and maintaining high quality software. Development teams are responsible for making code changes to address performance regressions, errors, or security vulnerabilities.
- infrastructure bool
- Responsible for the administration, management, and support of the IT infrastructure including physical servers, virtualization, and cloud. Teams with infrastructure responsibility are responsible for addressing hardware issues, resource limits, and operating system vulnerabilities.
- line_
of_ boolbusiness - Responsible for ensuring that applications in development align with business needs and meet the usability requirements of users, stakeholders, customers, and external partners. Teams with line of business responsibility are responsible for understanding the customer experience and how it affects business goals.
- operations bool
- Responsible for deploying and managing software, with a focus on high availability and performance. Teams with operations responsibilities needs to understand the impact, priority, and team responsible for addressing problems detected by Dynatrace.
- security bool
- Responsible for the security posture of the organization. Teams with security responsibility must understand the impact, priority, and team responsible for addressing security vulnerabilities.
- development Boolean
- Responsible for developing and maintaining high quality software. Development teams are responsible for making code changes to address performance regressions, errors, or security vulnerabilities.
- infrastructure Boolean
- Responsible for the administration, management, and support of the IT infrastructure including physical servers, virtualization, and cloud. Teams with infrastructure responsibility are responsible for addressing hardware issues, resource limits, and operating system vulnerabilities.
- line
Of BooleanBusiness - Responsible for ensuring that applications in development align with business needs and meet the usability requirements of users, stakeholders, customers, and external partners. Teams with line of business responsibility are responsible for understanding the customer experience and how it affects business goals.
- operations Boolean
- Responsible for deploying and managing software, with a focus on high availability and performance. Teams with operations responsibilities needs to understand the impact, priority, and team responsible for addressing problems detected by Dynatrace.
- security Boolean
- Responsible for the security posture of the organization. Teams with security responsibility must understand the impact, priority, and team responsible for addressing security vulnerabilities.
OwnershipTeamsSupplementaryIdentifiers, OwnershipTeamsSupplementaryIdentifiersArgs
OwnershipTeamsSupplementaryIdentifiersSupplementaryIdentifier, OwnershipTeamsSupplementaryIdentifiersSupplementaryIdentifierArgs
- Supplementary
Identifier string - Supplementary Identifier
- Supplementary
Identifier string - Supplementary Identifier
- supplementary
Identifier String - Supplementary Identifier
- supplementary
Identifier string - Supplementary Identifier
- supplementary_
identifier str - Supplementary Identifier
- supplementary
Identifier String - Supplementary Identifier
Package Details
- Repository
- dynatrace pulumiverse/pulumi-dynatrace
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
dynatrace
Terraform Provider.