@pulumi/auth0 3.45.0-alpha.1779950169 → 3.45.0-alpha.1780121907

package/connection.d.ts

@@ -650,7 +650,7 @@ import * as outputs from "./types/output";
  *
  * ### Okta Connection
  *
- * !> When configuring an Okta Workforce connection, the `scopes` attribute must be explicitly set. If omitted, the connection may not function correctly.
+ * > When configuring an Okta Workforce connection, the `scopes` attribute must be explicitly set. If omitted, the connection may not function correctly.
  * To ensure proper behavior, always specify:  `scopes = ["openid", "profile", "email"]`
  *
  * ```typescript

package/connection.js

@@ -677,7 +677,7 @@ const utilities = __importStar(require("./utilities"));
  *
  * ### Okta Connection
  *
- * !> When configuring an Okta Workforce connection, the `scopes` attribute must be explicitly set. If omitted, the connection may not function correctly.
+ * > When configuring an Okta Workforce connection, the `scopes` attribute must be explicitly set. If omitted, the connection may not function correctly.
  * To ensure proper behavior, always specify:  `scopes = ["openid", "profile", "email"]`
  *
  * ```typescript

package/connectionClient.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * With this resource, you can enable a single client on a connection.
  *
- * !> This resource appends an enabled client to a connection. In contrast, the `auth0.ConnectionClients` resource
+ * > This resource appends an enabled client to a connection. In contrast, the `auth0.ConnectionClients` resource
  * manages all the clients enabled for a connection. To avoid potential issues, it is recommended not to use this
  * resource in conjunction with the `auth0.ConnectionClients` resource when managing enabled clients for the
  * same connection id.

package/connectionClient.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can enable a single client on a connection.
  *
- * !> This resource appends an enabled client to a connection. In contrast, the `auth0.ConnectionClients` resource
+ * > This resource appends an enabled client to a connection. In contrast, the `auth0.ConnectionClients` resource
  * manages all the clients enabled for a connection. To avoid potential issues, it is recommended not to use this
  * resource in conjunction with the `auth0.ConnectionClients` resource when managing enabled clients for the
  * same connection id.

package/connectionClients.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * With this resource, you can manage all of the enabled clients on a connection.
  *
- * !> This resource manages all the enabled clients for a connection. In contrast, the `auth0.ConnectionClient` resource
+ * > This resource manages all the enabled clients for a connection. In contrast, the `auth0.ConnectionClient` resource
  * appends an enabled client to a connection. To avoid potential issues, it is recommended not to use this
  * resource in conjunction with the `auth0.ConnectionClient` resource when managing enabled clients for the same
  * connection id.

package/connectionClients.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can manage all of the enabled clients on a connection.
  *
- * !> This resource manages all the enabled clients for a connection. In contrast, the `auth0.ConnectionClient` resource
+ * > This resource manages all the enabled clients for a connection. In contrast, the `auth0.ConnectionClient` resource
  * appends an enabled client to a connection. To avoid potential issues, it is recommended not to use this
  * resource in conjunction with the `auth0.ConnectionClient` resource when managing enabled clients for the same
  * connection id.

package/connectionKeys.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * Client Assertion JWT is a more secure alternative to client secret authentication for OIDC and Okta Workforce connections. It uses a signed JWT instead of a shared secret to authenticate the client. The resource only supports key rotation. Use the auth0.ConnectionKeys data source to read existing keys. Removing the resource from configuration will NOT DELETE the key.
  *
- * !> The triggers field is only a placeholder for an arbitrary map used to signal the provider
+ * > The triggers field is only a placeholder for an arbitrary map used to signal the provider
  * to perform a key rotation whenever any update is made.
  * If the resource is removed from the configuration, the keys will not be deleted.
  *

package/connectionKeys.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * Client Assertion JWT is a more secure alternative to client secret authentication for OIDC and Okta Workforce connections. It uses a signed JWT instead of a shared secret to authenticate the client. The resource only supports key rotation. Use the auth0.ConnectionKeys data source to read existing keys. Removing the resource from configuration will NOT DELETE the key.
  *
- * !> The triggers field is only a placeholder for an arbitrary map used to signal the provider
+ * > The triggers field is only a placeholder for an arbitrary map used to signal the provider
  * to perform a key rotation whenever any update is made.
  * If the resource is removed from the configuration, the keys will not be deleted.
  *

package/emailProvider.d.ts

@@ -4,10 +4,10 @@ import * as outputs from "./types/output";
 /**
  * With Auth0, you can have standard welcome, password reset, and account verification email-based workflows built right into Auth0. This resource allows you to configure email providers, so you can route all emails that are part of Auth0's authentication workflows through the supported high-volume email service of your choice.
  *
- * !> This resource manages to create a max of 1 email provider for a tenant.
+ * > This resource manages to create a max of 1 email provider for a tenant.
  * To avoid potential issues, it is recommended not to try creating multiple email providers on the same tenant.
  *
- * !> If you are using the `auth0.EmailProvider` resource to create a `custom` email provider, you must ensure an action is created first with `custom-email-provider` as the supportedTriggers
+ * > If you are using the `auth0.EmailProvider` resource to create a `custom` email provider, you must ensure an action is created first with `custom-email-provider` as the supportedTriggers
  *
  * ## Example Usage
  *

package/emailProvider.js

@@ -31,10 +31,10 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With Auth0, you can have standard welcome, password reset, and account verification email-based workflows built right into Auth0. This resource allows you to configure email providers, so you can route all emails that are part of Auth0's authentication workflows through the supported high-volume email service of your choice.
  *
- * !> This resource manages to create a max of 1 email provider for a tenant.
+ * > This resource manages to create a max of 1 email provider for a tenant.
  * To avoid potential issues, it is recommended not to try creating multiple email providers on the same tenant.
  *
- * !> If you are using the `auth0.EmailProvider` resource to create a `custom` email provider, you must ensure an action is created first with `custom-email-provider` as the supportedTriggers
+ * > If you are using the `auth0.EmailProvider` resource to create a `custom` email provider, you must ensure an action is created first with `custom-email-provider` as the supportedTriggers
  *
  * ## Example Usage
  *

package/hook.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * Hooks are secure, self-contained functions that allow you to customize the behavior of Auth0 when executed for selected extensibility points of the Auth0 platform. Auth0 invokes Hooks during runtime to execute your custom Node.js code. Depending on the extensibility point, you can use hooks with Database Connections and/or Passwordless Connections.
  *
- * !> This resource is deprecated. Refer to the [guide on how to migrate from hooks to actions](https://auth0.com/docs/customize/actions/migrate/migrate-from-hooks-to-actions) and manage your actions using the `auth0.Action` resource.
+ * > This resource is deprecated. Refer to the [guide on how to migrate from hooks to actions](https://auth0.com/docs/customize/actions/migrate/migrate-from-hooks-to-actions) and manage your actions using the `auth0.Action` resource.
  *
  * ## Example Usage
  *

package/hook.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * Hooks are secure, self-contained functions that allow you to customize the behavior of Auth0 when executed for selected extensibility points of the Auth0 platform. Auth0 invokes Hooks during runtime to execute your custom Node.js code. Depending on the extensibility point, you can use hooks with Database Connections and/or Passwordless Connections.
  *
- * !> This resource is deprecated. Refer to the [guide on how to migrate from hooks to actions](https://auth0.com/docs/customize/actions/migrate/migrate-from-hooks-to-actions) and manage your actions using the `auth0.Action` resource.
+ * > This resource is deprecated. Refer to the [guide on how to migrate from hooks to actions](https://auth0.com/docs/customize/actions/migrate/migrate-from-hooks-to-actions) and manage your actions using the `auth0.Action` resource.
  *
  * ## Example Usage
  *

package/logStream.d.ts

@@ -4,7 +4,7 @@ import * as outputs from "./types/output";
 /**
  * With this resource, you can manage your Auth0 log streams.
  *
- * !> isPriority is a field that can be set while the resource is being created.
+ * > isPriority is a field that can be set while the resource is being created.
  * This cannot be updated once set. Updating the value might result in a noisy plan.
  *
  * ## Example Usage

package/logStream.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can manage your Auth0 log streams.
  *
- * !> isPriority is a field that can be set while the resource is being created.
+ * > isPriority is a field that can be set while the resource is being created.
  * This cannot be updated once set. Updating the value might result in a noisy plan.
  *
  * ## Example Usage

package/organizationConnection.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * With this resource, you can manage enabled connections on an organization.
  *
- * !> This resource appends a connection to an organization. In contrast, the `auth0.OrganizationConnections` resource
+ * > This resource appends a connection to an organization. In contrast, the `auth0.OrganizationConnections` resource
  * manages all the connections enabled for an organization. To avoid potential issues, it is recommended not to use this
  * resource in conjunction with the `auth0.OrganizationConnections` resource when managing enabled connections for the
  * same organization id.

package/organizationConnection.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can manage enabled connections on an organization.
  *
- * !> This resource appends a connection to an organization. In contrast, the `auth0.OrganizationConnections` resource
+ * > This resource appends a connection to an organization. In contrast, the `auth0.OrganizationConnections` resource
  * manages all the connections enabled for an organization. To avoid potential issues, it is recommended not to use this
  * resource in conjunction with the `auth0.OrganizationConnections` resource when managing enabled connections for the
  * same organization id.

package/organizationConnections.d.ts

@@ -4,7 +4,7 @@ import * as outputs from "./types/output";
 /**
  * With this resource, you can manage enabled connections on an organization.
  *
- * !> This resource manages all the connections enabled for an organization. In contrast, the `auth0.OrganizationConnection`
+ * > This resource manages all the connections enabled for an organization. In contrast, the `auth0.OrganizationConnection`
  * resource appends a connection to an organization. To avoid potential issues, it is recommended not to use this
  * resource in conjunction with the `auth0.OrganizationConnection` resource when managing connections for the same
  * organization id.

package/organizationConnections.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can manage enabled connections on an organization.
  *
- * !> This resource manages all the connections enabled for an organization. In contrast, the `auth0.OrganizationConnection`
+ * > This resource manages all the connections enabled for an organization. In contrast, the `auth0.OrganizationConnection`
  * resource appends a connection to an organization. To avoid potential issues, it is recommended not to use this
  * resource in conjunction with the `auth0.OrganizationConnection` resource when managing connections for the same
  * organization id.

package/organizationMember.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * This resource is used to manage the assignment of members and their roles within an organization.
  *
- * !> This resource appends a member to an organization. In contrast, the `auth0.OrganizationMembers` resource manages
+ * > This resource appends a member to an organization. In contrast, the `auth0.OrganizationMembers` resource manages
  * all the members assigned to an organization. To avoid potential issues, it is recommended not to use this resource in
  * conjunction with the `auth0.OrganizationMembers` resource when managing members for the same organization id.
  *

package/organizationMember.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * This resource is used to manage the assignment of members and their roles within an organization.
  *
- * !> This resource appends a member to an organization. In contrast, the `auth0.OrganizationMembers` resource manages
+ * > This resource appends a member to an organization. In contrast, the `auth0.OrganizationMembers` resource manages
  * all the members assigned to an organization. To avoid potential issues, it is recommended not to use this resource in
  * conjunction with the `auth0.OrganizationMembers` resource when managing members for the same organization id.
  *

package/organizationMembers.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * This resource is used to manage members of an organization.
  *
- * !> This resource manages all the members assigned to an organization. In contrast, the `auth0.OrganizationMember`
+ * > This resource manages all the members assigned to an organization. In contrast, the `auth0.OrganizationMember`
  * resource only appends a member to an organization. To avoid potential issues, it is recommended not to use this
  * resource in conjunction with the `auth0.OrganizationMember` resource when managing members for the same organization
  * id.

package/organizationMembers.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * This resource is used to manage members of an organization.
  *
- * !> This resource manages all the members assigned to an organization. In contrast, the `auth0.OrganizationMember`
+ * > This resource manages all the members assigned to an organization. In contrast, the `auth0.OrganizationMember`
  * resource only appends a member to an organization. To avoid potential issues, it is recommended not to use this
  * resource in conjunction with the `auth0.OrganizationMember` resource when managing members for the same organization
  * id.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@pulumi/auth0",
-    "version": "3.45.0-alpha.1779950169",
+    "version": "3.45.0-alpha.1780121907",
     "description": "A Pulumi package for creating and managing auth0 cloud resources.",
     "keywords": [
         "pulumi",
@@ -23,6 +23,6 @@
     "pulumi": {
         "resource": true,
         "name": "auth0",
-        "version": "3.45.0-alpha.1779950169"
+        "version": "3.45.0-alpha.1780121907"
     }
 }

package/pages.d.ts

@@ -4,7 +4,7 @@ import * as outputs from "./types/output";
 /**
  * With this resource you can manage custom HTML for the Login, Reset Password, Multi-Factor Authentication and Error pages.
  *
- * !> The error block in auth0.Pages is not recommended when you're managing tenant settings via the auth0.Tenant resource.
+ * > The error block in auth0.Pages is not recommended when you're managing tenant settings via the auth0.Tenant resource.
  * To avoid conflicts, configure the errorPage directly in auth0.Tenant instead.
  *
  * ## Example Usage

package/pages.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource you can manage custom HTML for the Login, Reset Password, Multi-Factor Authentication and Error pages.
  *
- * !> The error block in auth0.Pages is not recommended when you're managing tenant settings via the auth0.Tenant resource.
+ * > The error block in auth0.Pages is not recommended when you're managing tenant settings via the auth0.Tenant resource.
  * To avoid conflicts, configure the errorPage directly in auth0.Tenant instead.
  *
  * ## Example Usage

package/phoneProvider.d.ts

@@ -4,10 +4,10 @@ import * as outputs from "./types/output";
 /**
  * Auth0 allows you to configure your own phone messaging provider to help you manage, monitor, and troubleshoot your SMS and voice communications. You can only configure one phone provider for all SMS and voice communications per tenant.
  *
- * !> This resource manages to create a max of 1 phone provider for a tenant.
+ * > This resource manages to create a max of 1 phone provider for a tenant.
  * To avoid potential issues, it is recommended not to try creating multiple phone providers on the same tenant.
  *
- * !> If you are using the `auth0.PhoneProvider` resource to create a `custom` phone provider, you must ensure an action is created first with `custom-phone-provider` as the supportedTriggers
+ * > If you are using the `auth0.PhoneProvider` resource to create a `custom` phone provider, you must ensure an action is created first with `custom-phone-provider` as the supportedTriggers
  *
  * ## Example Usage
  *

package/phoneProvider.js

@@ -31,10 +31,10 @@ const utilities = __importStar(require("./utilities"));
 /**
  * Auth0 allows you to configure your own phone messaging provider to help you manage, monitor, and troubleshoot your SMS and voice communications. You can only configure one phone provider for all SMS and voice communications per tenant.
  *
- * !> This resource manages to create a max of 1 phone provider for a tenant.
+ * > This resource manages to create a max of 1 phone provider for a tenant.
  * To avoid potential issues, it is recommended not to try creating multiple phone providers on the same tenant.
  *
- * !> If you are using the `auth0.PhoneProvider` resource to create a `custom` phone provider, you must ensure an action is created first with `custom-phone-provider` as the supportedTriggers
+ * > If you are using the `auth0.PhoneProvider` resource to create a `custom` phone provider, you must ensure an action is created first with `custom-phone-provider` as the supportedTriggers
  *
  * ## Example Usage
  *

package/promptPartials.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * With this resource, you can manage a customized sign up and login experience by adding custom content, form elements and css/javascript. You can read more about this [here](https://auth0.com/docs/customize/universal-login-pages/customize-signup-and-login-prompts).
  *
- * !> **Deprecated:** `auth0.PromptPartials` has been deprecated. Please use `auth0.PromptScreenPartials` for managing multiple
+ * > **Deprecated:** `auth0.PromptPartials` has been deprecated. Please use `auth0.PromptScreenPartials` for managing multiple
  * prompt screens or `auth0.PromptScreenPartial` for managing a single prompt screen.
  *
  * ## Example Usage

package/promptPartials.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can manage a customized sign up and login experience by adding custom content, form elements and css/javascript. You can read more about this [here](https://auth0.com/docs/customize/universal-login-pages/customize-signup-and-login-prompts).
  *
- * !> **Deprecated:** `auth0.PromptPartials` has been deprecated. Please use `auth0.PromptScreenPartials` for managing multiple
+ * > **Deprecated:** `auth0.PromptPartials` has been deprecated. Please use `auth0.PromptScreenPartials` for managing multiple
  * prompt screens or `auth0.PromptScreenPartial` for managing a single prompt screen.
  *
  * ## Example Usage

package/promptScreenPartial.d.ts

@@ -4,7 +4,7 @@ import * as outputs from "./types/output";
 /**
  * With this resource, you can manage a customized sign up and login experience by adding custom content, form elements and css/javascript. You can read more about this [here](https://auth0.com/docs/customize/universal-login-pages/customize-signup-and-login-prompts).
  *
- * !> This resource appends a specific prompt screen to the list of prompt screens displayed to the user during the authentication flow.
+ * > This resource appends a specific prompt screen to the list of prompt screens displayed to the user during the authentication flow.
  *  In contrast, the `auth0.PromptScreenPartials` resource manages the complete set of prompt screens that are displayed during the
  *  authentication flow. To avoid potential issues, it is recommended not to use this resource in conjunction with the
  *  `auth0.PromptScreenPartials` resource when managing prompt screens for the same prompt.

package/promptScreenPartial.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can manage a customized sign up and login experience by adding custom content, form elements and css/javascript. You can read more about this [here](https://auth0.com/docs/customize/universal-login-pages/customize-signup-and-login-prompts).
  *
- * !> This resource appends a specific prompt screen to the list of prompt screens displayed to the user during the authentication flow.
+ * > This resource appends a specific prompt screen to the list of prompt screens displayed to the user during the authentication flow.
  *  In contrast, the `auth0.PromptScreenPartials` resource manages the complete set of prompt screens that are displayed during the
  *  authentication flow. To avoid potential issues, it is recommended not to use this resource in conjunction with the
  *  `auth0.PromptScreenPartials` resource when managing prompt screens for the same prompt.

package/promptScreenPartials.d.ts

@@ -4,7 +4,7 @@ import * as outputs from "./types/output";
 /**
  * With this resource, you can manage a customized sign up and login experience by adding custom content, form elements and css/javascript. You can read more about this [here](https://auth0.com/docs/customize/universal-login-pages/customize-signup-and-login-prompts).
  *
- * !> This resource manages the entire set of prompt screens enabled for a prompt. In contrast, the `auth0.PromptScreenPartial`
+ * > This resource manages the entire set of prompt screens enabled for a prompt. In contrast, the `auth0.PromptScreenPartial`
  * resource appends a specific prompt screen to the list of prompt screens displayed to the user during the authentication flow.
  *  To avoid potential issues, it is recommended not to use this resource in conjunction with the `auth0.PromptScreenPartial`
  *  resource when managing prompt screens for the same prompt.

package/promptScreenPartials.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can manage a customized sign up and login experience by adding custom content, form elements and css/javascript. You can read more about this [here](https://auth0.com/docs/customize/universal-login-pages/customize-signup-and-login-prompts).
  *
- * !> This resource manages the entire set of prompt screens enabled for a prompt. In contrast, the `auth0.PromptScreenPartial`
+ * > This resource manages the entire set of prompt screens enabled for a prompt. In contrast, the `auth0.PromptScreenPartial`
  * resource appends a specific prompt screen to the list of prompt screens displayed to the user during the authentication flow.
  *  To avoid potential issues, it is recommended not to use this resource in conjunction with the `auth0.PromptScreenPartial`
  *  resource when managing prompt screens for the same prompt.

package/resourceServerScope.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * With this resource, you can manage scopes (permissions) associated with a resource server (API).
  *
- * !> This resource appends a scope to a resource server. In contrast, the `auth0.ResourceServerScopes` resource manages
+ * > This resource appends a scope to a resource server. In contrast, the `auth0.ResourceServerScopes` resource manages
  * all the scopes assigned to a resource server. To avoid potential issues, it is recommended not to use this resource in
  * conjunction with the `auth0.ResourceServerScopes` resource when managing scopes for the same resource server id.
  *

package/resourceServerScope.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can manage scopes (permissions) associated with a resource server (API).
  *
- * !> This resource appends a scope to a resource server. In contrast, the `auth0.ResourceServerScopes` resource manages
+ * > This resource appends a scope to a resource server. In contrast, the `auth0.ResourceServerScopes` resource manages
  * all the scopes assigned to a resource server. To avoid potential issues, it is recommended not to use this resource in
  * conjunction with the `auth0.ResourceServerScopes` resource when managing scopes for the same resource server id.
  *

package/resourceServerScopes.d.ts

@@ -4,7 +4,7 @@ import * as outputs from "./types/output";
 /**
  * With this resource, you can manage scopes (permissions) associated with a resource server (API).
  *
- * !> This resource manages all the scopes assigned to a resource server. In contrast, the `auth0.ResourceServerScope`
+ * > This resource manages all the scopes assigned to a resource server. In contrast, the `auth0.ResourceServerScope`
  * resource only appends a scope to a resource server. To avoid potential issues, it is recommended not to use this
  * resource in conjunction with the `auth0.ResourceServerScope` resource when managing scopes for the same resource
  * server id.

package/resourceServerScopes.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can manage scopes (permissions) associated with a resource server (API).
  *
- * !> This resource manages all the scopes assigned to a resource server. In contrast, the `auth0.ResourceServerScope`
+ * > This resource manages all the scopes assigned to a resource server. In contrast, the `auth0.ResourceServerScope`
  * resource only appends a scope to a resource server. To avoid potential issues, it is recommended not to use this
  * resource in conjunction with the `auth0.ResourceServerScope` resource when managing scopes for the same resource
  * server id.

package/rolePermission.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * With this resource, you can manage role permissions (1-1).
  *
- * !> This resource appends a permission to a role. In contrast, the `auth0.RolePermissions` resource manages all the
+ * > This resource appends a permission to a role. In contrast, the `auth0.RolePermissions` resource manages all the
  * permissions assigned to a role. To avoid potential issues, it is recommended not to use this resource in conjunction
  * with the `auth0.RolePermissions` resource when managing permissions for the same role id.
  *

package/rolePermission.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can manage role permissions (1-1).
  *
- * !> This resource appends a permission to a role. In contrast, the `auth0.RolePermissions` resource manages all the
+ * > This resource appends a permission to a role. In contrast, the `auth0.RolePermissions` resource manages all the
  * permissions assigned to a role. To avoid potential issues, it is recommended not to use this resource in conjunction
  * with the `auth0.RolePermissions` resource when managing permissions for the same role id.
  *

package/rolePermissions.d.ts

@@ -4,7 +4,7 @@ import * as outputs from "./types/output";
 /**
  * With this resource, you can manage role permissions (1-many).
  *
- * !> This resource manages all the permissions assigned to a role. In contrast, the `auth0.RolePermission` resource only
+ * > This resource manages all the permissions assigned to a role. In contrast, the `auth0.RolePermission` resource only
  * appends a permission to a role. To avoid potential issues, it is recommended not to use this resource in conjunction
  * with the `auth0.RolePermission` resource when managing permissions for the same role id.
  *

package/rolePermissions.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can manage role permissions (1-many).
  *
- * !> This resource manages all the permissions assigned to a role. In contrast, the `auth0.RolePermission` resource only
+ * > This resource manages all the permissions assigned to a role. In contrast, the `auth0.RolePermission` resource only
  * appends a permission to a role. To avoid potential issues, it is recommended not to use this resource in conjunction
  * with the `auth0.RolePermission` resource when managing permissions for the same role id.
  *

package/rule.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * With Auth0, you can create custom Javascript snippets that run in a secure, isolated sandbox as part of your authentication pipeline, which are otherwise known as rules. This resource allows you to create and manage rules. You can create global variable for use with rules by using the `auth0.RuleConfig` resource.
  *
- * !> This resource is deprecated. Refer to the [guide on how to migrate from rules to actions](https://auth0.com/docs/customize/actions/migrate/migrate-from-rules-to-actions) and manage your actions using the `auth0.Action` resource.
+ * > This resource is deprecated. Refer to the [guide on how to migrate from rules to actions](https://auth0.com/docs/customize/actions/migrate/migrate-from-rules-to-actions) and manage your actions using the `auth0.Action` resource.
  *
  * ## Example Usage
  *

package/rule.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With Auth0, you can create custom Javascript snippets that run in a secure, isolated sandbox as part of your authentication pipeline, which are otherwise known as rules. This resource allows you to create and manage rules. You can create global variable for use with rules by using the `auth0.RuleConfig` resource.
  *
- * !> This resource is deprecated. Refer to the [guide on how to migrate from rules to actions](https://auth0.com/docs/customize/actions/migrate/migrate-from-rules-to-actions) and manage your actions using the `auth0.Action` resource.
+ * > This resource is deprecated. Refer to the [guide on how to migrate from rules to actions](https://auth0.com/docs/customize/actions/migrate/migrate-from-rules-to-actions) and manage your actions using the `auth0.Action` resource.
  *
  * ## Example Usage
  *

package/triggerAction.d.ts

@@ -4,7 +4,7 @@ import * as pulumi from "@pulumi/pulumi";
  *
  * Ordering of an action within a specific flow is not currently supported when using this resource; the action will get appended to the end of the flow. To precisely manage ordering, it is advised to either do so with the dashboard UI or with the `auth0TriggerBindings` resource.
  *
- * !> This resource appends an action to the trigger binding. In contrast, the `auth0.TriggerActions` resource manages all
+ * > This resource appends an action to the trigger binding. In contrast, the `auth0.TriggerActions` resource manages all
  * the action bindings to a trigger. To avoid potential issues, it is recommended not to use this resource in conjunction
  * with the `auth0.TriggerAction` resource when binding actions to the same trigger.
  *

package/triggerAction.js

@@ -33,7 +33,7 @@ const utilities = __importStar(require("./utilities"));
  *
  * Ordering of an action within a specific flow is not currently supported when using this resource; the action will get appended to the end of the flow. To precisely manage ordering, it is advised to either do so with the dashboard UI or with the `auth0TriggerBindings` resource.
  *
- * !> This resource appends an action to the trigger binding. In contrast, the `auth0.TriggerActions` resource manages all
+ * > This resource appends an action to the trigger binding. In contrast, the `auth0.TriggerActions` resource manages all
  * the action bindings to a trigger. To avoid potential issues, it is recommended not to use this resource in conjunction
  * with the `auth0.TriggerAction` resource when binding actions to the same trigger.
  *

package/triggerActions.d.ts

@@ -4,7 +4,7 @@ import * as outputs from "./types/output";
 /**
  * With this resource, you can bind actions to a trigger. Once actions are created and deployed, they can be attached (i.e. bound) to a trigger so that it will be executed as part of a flow. The list of actions reflects the order in which they will be executed during the appropriate flow.
  *
- * !> This resource manages all the action bindings to a trigger. In contrast, the `auth0.TriggerAction` resource only
+ * > This resource manages all the action bindings to a trigger. In contrast, the `auth0.TriggerAction` resource only
  * appends an action to the trigger binding. To avoid potential issues, it is recommended not to use this resource in
  * conjunction with the `auth0.TriggerAction` resource when binding actions to the same trigger.
  *

package/triggerActions.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can bind actions to a trigger. Once actions are created and deployed, they can be attached (i.e. bound) to a trigger so that it will be executed as part of a flow. The list of actions reflects the order in which they will be executed during the appropriate flow.
  *
- * !> This resource manages all the action bindings to a trigger. In contrast, the `auth0.TriggerAction` resource only
+ * > This resource manages all the action bindings to a trigger. In contrast, the `auth0.TriggerAction` resource only
  * appends an action to the trigger binding. To avoid potential issues, it is recommended not to use this resource in
  * conjunction with the `auth0.TriggerAction` resource when binding actions to the same trigger.
  *

package/userPermission.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * With this resource, you can manage user permissions.
  *
- * !> This resource appends a permission to a user. In contrast, the `auth0.UserPermissions` resource manages all the
+ * > This resource appends a permission to a user. In contrast, the `auth0.UserPermissions` resource manages all the
  * permissions assigned to a user. To avoid potential issues, it is recommended not to use this resource in conjunction
  * with the `auth0.UserPermissions` resource when managing permissions for the same user id.
  *

package/userPermission.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can manage user permissions.
  *
- * !> This resource appends a permission to a user. In contrast, the `auth0.UserPermissions` resource manages all the
+ * > This resource appends a permission to a user. In contrast, the `auth0.UserPermissions` resource manages all the
  * permissions assigned to a user. To avoid potential issues, it is recommended not to use this resource in conjunction
  * with the `auth0.UserPermissions` resource when managing permissions for the same user id.
  *

package/userPermissions.d.ts

@@ -4,7 +4,7 @@ import * as outputs from "./types/output";
 /**
  * With this resource, you can manage all of a user's permissions.
  *
- * !> This resource manages all the permissions assigned to a user. In contrast, the `auth0.UserPermission` resource only
+ * > This resource manages all the permissions assigned to a user. In contrast, the `auth0.UserPermission` resource only
  * appends a permissions to a user. To avoid potential issues, it is recommended not to use this resource in conjunction
  * with the `auth0.UserPermission` resource when managing permissions for the same user id.
  *

package/userPermissions.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can manage all of a user's permissions.
  *
- * !> This resource manages all the permissions assigned to a user. In contrast, the `auth0.UserPermission` resource only
+ * > This resource manages all the permissions assigned to a user. In contrast, the `auth0.UserPermission` resource only
  * appends a permissions to a user. To avoid potential issues, it is recommended not to use this resource in conjunction
  * with the `auth0.UserPermission` resource when managing permissions for the same user id.
  *

package/userRole.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * With this resource, you can manage assigned roles for a user.
  *
- * !> This resource appends a role to a user. In contrast, the `auth0.UserRoles` resource manages all the roles assigned
+ * > This resource appends a role to a user. In contrast, the `auth0.UserRoles` resource manages all the roles assigned
  * to a user. To avoid potential issues, it is recommended not to use this resource in conjunction with the
  * `auth0.UserRoles` resource when managing roles for the same user id.
  *

package/userRole.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can manage assigned roles for a user.
  *
- * !> This resource appends a role to a user. In contrast, the `auth0.UserRoles` resource manages all the roles assigned
+ * > This resource appends a role to a user. In contrast, the `auth0.UserRoles` resource manages all the roles assigned
  * to a user. To avoid potential issues, it is recommended not to use this resource in conjunction with the
  * `auth0.UserRoles` resource when managing roles for the same user id.
  *

package/userRoles.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * With this resource, you can manage assigned roles for a user.
  *
- * !> This resource manages all the roles assigned to a user. In contrast, the `auth0.UserRole` resource only appends a
+ * > This resource manages all the roles assigned to a user. In contrast, the `auth0.UserRole` resource only appends a
  * role to a user. To avoid potential issues, it is recommended not to use this resource in conjunction with the
  * `auth0.UserRole` resource when managing roles for the same user id.
  *

package/userRoles.js

@@ -31,7 +31,7 @@ const utilities = __importStar(require("./utilities"));
 /**
  * With this resource, you can manage assigned roles for a user.
  *
- * !> This resource manages all the roles assigned to a user. In contrast, the `auth0.UserRole` resource only appends a
+ * > This resource manages all the roles assigned to a user. In contrast, the `auth0.UserRole` resource only appends a
  * role to a user. To avoid potential issues, it is recommended not to use this resource in conjunction with the
  * `auth0.UserRole` resource when managing roles for the same user id.
  *