Skip to main content

CatalogRecord

Resource CatalogRecord in pulumi-better-uptime.
4 min read

Resource CatalogRecord in pulumi-better-uptime.

Pulumi type: better-uptime:index/catalogRecord:CatalogRecord.

name is the Pulumi resource name. Nested object fields are documented under that object. They are not arguments of this resource.

Example#

Only required arguments are set. A string in angle brackets stands in for that argument. Any other value is an option or example written in the SDK description.

Arguments#

PropertyTypeRequiredDescription
attributesCatalogRecordAttribute (input)[]yesList of attribute values for the Catalog record. You can have multiple blocks with same attributeId for multiple values.
relationIdstringyesThe ID of the Catalog relation this record belongs to.

Outputs#

Computed outputs are produced by the provider. They are not constructor arguments.

PropertyTypeComputedDescription
attributesCatalogRecordAttribute (output)[]noList of attribute values for the Catalog record. You can have multiple blocks with same attributeId for multiple values.
relationIdstringnoThe ID of the Catalog relation this record belongs to.

CatalogRecordAttribute (input)#

Input object CatalogRecordAttribute. Fields below belong to this object, not to the parent.

PropertyTypeRequiredDescription
attributeIdstringyesID of the target Catalog attribute.
attributeNamestringnoName of the Catalog attribute.
emailstringnoEmail of the referenced user when type is User.
itemIdstringnoID of the referenced item when type is different than String.
namestringnoName of the referenced item when type is different than String. Not available for Endpoint, SlackIntegration, and ZapierWebhook, which are referenced by itemId.
typestringnoValue types can be grouped into 2 main categories: - Scalar: String - Reference: User, Team, Policy, Schedule, Endpoint, Source, SlackIntegration, LinearIntegration, JiraIntegration, MicrosoftTeamsWebhook, ZapierWebhook, NativeWebhook, PagerDutyWebhook The value of a Scalar type is defined using the value field. The value of a Reference type is defined using one of the following fields: - itemId - great choice when you know the ID of the target item. - email - your go-to choice when you're referencing users. - name - can be used to reference other items like teams, policies, etc. Not available for Endpoint, SlackIntegration, and ZapierWebhook, which are referenced by itemId. The reference types require the presence of at least one of the three fields: itemId, name, email.
valuestringnoValue when type is String.

CatalogRecordAttribute (output)#

Output object CatalogRecordAttribute. Fields below belong to this object.

PropertyTypeAlways presentDescription
attributeIdstringyesID of the target Catalog attribute.
attributeNamestringyesName of the Catalog attribute.
emailstringnoEmail of the referenced user when type is User.
itemIdstringnoID of the referenced item when type is different than String.
namestringnoName of the referenced item when type is different than String. Not available for Endpoint, SlackIntegration, and ZapierWebhook, which are referenced by itemId.
typestringnoValue types can be grouped into 2 main categories: - Scalar: String - Reference: User, Team, Policy, Schedule, Endpoint, Source, SlackIntegration, LinearIntegration, JiraIntegration, MicrosoftTeamsWebhook, ZapierWebhook, NativeWebhook, PagerDutyWebhook The value of a Scalar type is defined using the value field. The value of a Reference type is defined using one of the following fields: - itemId - great choice when you know the ID of the target item. - email - your go-to choice when you're referencing users. - name - can be used to reference other items like teams, policies, etc. Not available for Endpoint, SlackIntegration, and ZapierWebhook, which are referenced by itemId. The reference types require the presence of at least one of the three fields: itemId, name, email.
valuestringnoValue when type is String.