@sst-community/sst 4.21.1 → 5.0.0-alpha.2

package/platform/types/components/aws/efs.d.ts

@@ -0,0 +1,217 @@
+import { ComponentResourceOptions, Output } from "@pulumi/pulumi";
+import { Component, Transform } from "../component.js";
+import { Input } from "../input.js";
+import { ec2, efs } from "@pulumi/aws";
+import { Vpc } from "./vpc.js";
+export interface EfsArgs {
+    /**
+     * The throughput mode for the EFS file system.
+     *
+     * The default `elastic` mode scales up or down based on the workload. However, if you know
+     * your access patterns, you can use `provisioned` to have a fixed throughput.
+     *
+     * Or you can use `bursting` to scale with the amount of storage you're using. It also
+     * supports bursting to higher levels for up to 12 hours per day.
+     *
+     * @default `"elastic"`
+     *
+     * @example
+     * ```ts
+     * {
+     *   throughput: "bursting"
+     * }
+     * ```
+     */
+    throughput?: Input<"provisioned" | "bursting" | "elastic">;
+    /**
+     * The performance mode for the EFS file system.
+     *
+     * The `max-io` mode can support higher throughput, but with slightly higher latency. It's
+     * recommended for larger workloads like data analysis or meadia processing.
+     *
+     * Both the modes are priced the same, but `general-purpose` is recommended for most use cases.
+     *
+     * @default `"general-purpose"`
+     * @example
+     * ```ts
+     * {
+     *   performance: "max-io"
+     * }
+     * ```
+     */
+    performance?: Input<"general-purpose" | "max-io">;
+    /**
+     * The VPC to use for the EFS file system.
+     *
+     * @example
+     * Create a VPC component.
+     *
+     * ```js
+     * const myVpc = new sst.aws.Vpc("MyVpc");
+     * ```
+     *
+     * And pass it in.
+     *
+     * ```js
+     * {
+     *   vpc: myVpc
+     * }
+     * ```
+     *
+     * Or pass in a custom VPC configuration.
+     *
+     * ```js
+     * {
+     *   vpc: {
+     *     subnets: ["subnet-0db7376a7ad4db5fd ", "subnet-06fc7ee8319b2c0ce"]
+     *   }
+     * }
+     * ```
+     */
+    vpc: Vpc | Input<{
+        /**
+         * The ID of the VPC.
+         */
+        id: Input<string>;
+        /**
+         * A list of subnet IDs in the VPC to create the EFS mount targets in.
+         */
+        subnets: Input<Input<string>[]>;
+    }>;
+    /**
+     * [Transform](/docs/components#transform) how this component creates its underlying
+     * resources.
+     */
+    transform?: {
+        /**
+         * Transform the EFS file system.
+         */
+        fileSystem?: Transform<efs.FileSystemArgs>;
+        /**
+         * Transform the EFS access point.
+         */
+        accessPoint?: Transform<efs.AccessPointArgs>;
+        /**
+         * Transform the security group for the EFS mount targets.
+         */
+        securityGroup?: Transform<ec2.SecurityGroupArgs>;
+    };
+}
+/**
+ * The `Efs` component lets you add [Amazon Elastic File System (EFS)](https://docs.aws.amazon.com/efs/latest/ug/whatisefs.html) to your app.
+ *
+ * @example
+ *
+ * #### Create the file system
+ *
+ * ```js title="sst.config.ts" {2}
+ * const vpc = new sst.aws.Vpc("MyVpc");
+ * const efs = new sst.aws.Efs("MyEfs", { vpc });
+ * ```
+ *
+ * This needs a VPC.
+ *
+ * #### Attach it to a Lambda function
+ *
+ * ```ts title="sst.config.ts" {4}
+ * new sst.aws.Function("MyFunction", {
+ *   vpc,
+ *   handler: "lambda.handler",
+ *   volume: { efs, path: "/mnt/efs" }
+ * });
+ * ```
+ *
+ * This is now mounted at `/mnt/efs` in the Lambda function.
+ *
+ * #### Attach it to a container
+ *
+ * ```ts title="sst.config.ts" {7}
+ * const cluster = new sst.aws.Cluster("MyCluster", { vpc });
+ * new sst.aws.Service("MyService", {
+ *   cluster,
+ *   public: {
+ *     ports: [{ listen: "80/http" }],
+ *   },
+ *   volumes: [
+ *     { efs, path: "/mnt/efs" }
+ *   ]
+ * });
+ * ```
+ *
+ * Mounted at `/mnt/efs` in the container.
+ *
+ * ---
+ *
+ * ### Cost
+ *
+ * By default this component uses _Regional (Multi-AZ) with Elastic Throughput_. The pricing is
+ * pay-per-use.
+ *
+ * - For storage: $0.30 per GB per month
+ * - For reads: $0.03 per GB per month
+ * - For writes: $0.06 per GB per month
+ *
+ * The above are rough estimates for _us-east-1_, check out the
+ * [EFS pricing](https://aws.amazon.com/efs/pricing/) for more details.
+ */
+export declare class Efs extends Component {
+    private _fileSystem;
+    private _accessPoint;
+    constructor(name: string, args: EfsArgs, opts?: ComponentResourceOptions);
+    /**
+     * The ID of the EFS file system.
+     */
+    get id(): Output<string>;
+    /**
+     * The ID of the EFS access point.
+     */
+    get accessPoint(): Output<string>;
+    /**
+     * The underlying [resources](/docs/components/#nodes) this component creates.
+     */
+    get nodes(): {
+        /**
+         * The Amazon EFS file system.
+         */
+        fileSystem: Output<import("@pulumi/aws/efs/fileSystem.js").FileSystem>;
+        /**
+         * The Amazon EFS access point.
+         */
+        accessPoint: Output<import("@pulumi/aws/efs/accessPoint.js").AccessPoint>;
+    };
+    /**
+     * Reference an existing EFS file system with the given file system ID. This is useful when
+     * you create a EFS file system in one stage and want to share it in another. It avoids
+     * having to create a new EFS file system in the other stage.
+     *
+     * :::tip
+     * You can use the `static get` method to share EFS file systems across stages.
+     * :::
+     *
+     * @param name The name of the component.
+     * @param fileSystemID The ID of the existing EFS file system.
+     * @param opts Resource options.
+     *
+     * @example
+     * Imagine you create a EFS file system in the `dev` stage. And in your personal stage
+     * `frank`, instead of creating a new file system, you want to share the same file system
+     * from `dev`.
+     *
+     * ```ts title="sst.config.ts"
+     * const efs = $app.stage === "frank"
+     *   ? sst.aws.Efs.get("MyEfs", "app-dev-myefs")
+     *   : new sst.aws.Efs("MyEfs", { vpc });
+     * ```
+     *
+     * Here `app-dev-myefs` is the ID of the file system created in the `dev` stage.
+     * You can find this by outputting the file system ID in the `dev` stage.
+     *
+     * ```ts title="sst.config.ts"
+     * return {
+     *   id: efs.id
+     * };
+     * ```
+     */
+    static get(name: string, fileSystemID: Input<string>, opts?: ComponentResourceOptions): Efs;
+}
+//# sourceMappingURL=efs.d.ts.map

package/platform/types/components/aws/efs.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"efs.d.ts","sourceRoot":"","sources":["../../../../src/components/aws/efs.ts"],"names":[],"mappings":"AAAA,OAAO,EAAO,wBAAwB,EAAE,MAAM,EAAU,MAAM,gBAAgB,CAAC;AAC/E,OAAO,EAAE,SAAS,EAAE,SAAS,EAAa,MAAM,iBAAiB,CAAC;AAClE,OAAO,EAAE,KAAK,EAAE,MAAM,aAAa,CAAC;AACpC,OAAO,EAAE,GAAG,EAAE,GAAG,EAAE,MAAM,aAAa,CAAC;AACvC,OAAO,EAAE,GAAG,EAAE,MAAM,UAAU,CAAC;AAG/B,MAAM,WAAW,OAAO;IACtB;;;;;;;;;;;;;;;;;OAiBG;IACH,UAAU,CAAC,EAAE,KAAK,CAAC,aAAa,GAAG,UAAU,GAAG,SAAS,CAAC,CAAC;IAC3D;;;;;;;;;;;;;;;OAeG;IACH,WAAW,CAAC,EAAE,KAAK,CAAC,iBAAiB,GAAG,QAAQ,CAAC,CAAC;IAClD;;;;;;;;;;;;;;;;;;;;;;;;;;;OA2BG;IACH,GAAG,EACC,GAAG,GACH,KAAK,CAAC;QACJ;;WAEG;QACH,EAAE,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;QAClB;;WAEG;QACH,OAAO,EAAE,KAAK,CAAC,KAAK,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;KACjC,CAAC,CAAC;IACP;;;OAGG;IACH,SAAS,CAAC,EAAE;QACV;;WAEG;QACH,UAAU,CAAC,EAAE,SAAS,CAAC,GAAG,CAAC,cAAc,CAAC,CAAC;QAC3C;;WAEG;QACH,WAAW,CAAC,EAAE,SAAS,CAAC,GAAG,CAAC,eAAe,CAAC,CAAC;QAC7C;;WAEG;QACH,aAAa,CAAC,EAAE,SAAS,CAAC,GAAG,CAAC,iBAAiB,CAAC,CAAC;KAClD,CAAC;CACH;AAQD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAwDG;AACH,qBAAa,GAAI,SAAQ,SAAS;IAChC,OAAO,CAAC,WAAW,CAAyB;IAC5C,OAAO,CAAC,YAAY,CAA0B;gBAElC,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,OAAO,EAAE,IAAI,CAAC,EAAE,wBAAwB;IAiJxE;;OAEG;IACH,IAAW,EAAE,mBAEZ;IAED;;OAEG;IACH,IAAW,WAAW,mBAErB;IAED;;OAEG;IACH,IAAW,KAAK;QAEZ;;WAEG;;QAEH;;WAEG;;MAGN;IAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OAgCG;WACW,GAAG,CACf,IAAI,EAAE,MAAM,EACZ,YAAY,EAAE,KAAK,CAAC,MAAM,CAAC,EAC3B,IAAI,CAAC,EAAE,wBAAwB;CAuBlC"}

package/platform/types/components/aws/email.d.ts

@@ -0,0 +1,370 @@
+import { ComponentResourceOptions, Output } from "@pulumi/pulumi";
+import { Component, Prettify, Transform } from "../component";
+import { Link } from "../link";
+import { Input } from "../input";
+import { Dns } from "../dns";
+import { sesv2 } from "@pulumi/aws";
+interface Events {
+    /**
+     * The name of the event.
+     */
+    name: Input<string>;
+    /**
+     * The types of events to send.
+     */
+    types: Input<Input<"send" | "reject" | "bounce" | "complaint" | "delivery" | "delivery-delay" | "rendering-failure" | "subscription" | "open" | "click">[]>;
+    /**
+     * The ARN of the SNS topic to send events to.
+     */
+    topic?: Input<string>;
+    /**
+     * The ARN of the EventBridge bus to send events to.
+     */
+    bus?: Input<string>;
+}
+export interface EmailArgs {
+    /**
+     * The email address or domain name that you want to send emails from.
+     *
+     * :::note
+     * You'll need to verify the email address or domain you are using.
+     * :::
+     *
+     * @example
+     *
+     * Using an email address as the sender. You'll need to verify the email address.
+     * When you deploy your app, you will receive an email from AWS SES with a link to verify the
+     * email address.
+     *
+     * ```ts
+     * {
+     *   sender: "john.smith@gmail.com"
+     * }
+     * ```
+     *
+     * Using a domain name as the sender. You'll need to verify that you own the domain.
+     * Once you verified, you can send emails from any email addresses in the domain.
+     *
+     * :::tip
+     * SST can automatically verify the domain for the `dns` adapter that's specified.
+     * :::
+     *
+     * To verify the domain, you need to add the verification records to your domain's DNS.
+     * This can be done automatically for the supported `dns` adapters.
+     *
+     * ```ts
+     * {
+     *   sender: "example.com"
+     * }
+     * ```
+     *
+     * If the domain is hosted on Cloudflare.
+     *
+     * ```ts
+     * {
+     *   sender: "example.com",
+     *   dns: sst.cloudflare.dns()
+     * }
+     * ```
+     */
+    sender: Input<string>;
+    /**
+     * The DNS adapter you want to use for managing DNS records. Only specify this if you
+     * are using a domain name as the `sender`.
+     *
+     * :::note
+     * If `dns` is set to `false`, you have to add the DNS records manually to verify
+     * the domain.
+     * :::
+     *
+     * @default `sst.aws.dns`
+     *
+     * @example
+     *
+     * Specify the hosted zone ID for the domain.
+     *
+     * ```js
+     * {
+     *   dns: sst.aws.dns({
+     *     zone: "Z2FDTNDATAQYW2"
+     *   })
+     * }
+     * ```
+     *
+     * Domain is hosted on Cloudflare.
+     *
+     * ```js
+     * {
+     *   dns: sst.cloudflare.dns()
+     * }
+     * ```
+     */
+    dns?: Input<false | (Dns & {})>;
+    /**
+     * The DMARC policy for the domain. This'll create a DNS record with the given DMARC policy.
+     * Only specify this if you are using a domain name as the `sender`.
+     *
+     * @default `"v=DMARC1; p=none;"`
+     *
+     * @example
+     * ```js
+     * {
+     *   dmarc: "v=DMARC1; p=quarantine; adkim=s; aspf=s;"
+     * }
+     * ```
+     */
+    dmarc?: Input<string>;
+    /**
+     * Configure a custom [MAIL FROM domain](https://docs.aws.amazon.com/ses/latest/dg/mail-from.html)
+     * for the emails you send. This sets the `Return-Path` (envelope sender) to use a subdomain of
+     * your own domain instead of the default `amazonses.com`. It improves SPF alignment for DMARC
+     * and routes bounce and complaint feedback through your domain.
+     *
+     * This'll create the required MX and SPF DNS records for the MAIL FROM subdomain.
+     *
+     * :::note
+     * This is only valid when `sender` is a domain. The MAIL FROM `domain` must be a subdomain
+     * of the `sender` domain.
+     * :::
+     *
+     * @default No custom MAIL FROM domain
+     *
+     * @example
+     * ```js
+     * {
+     *   mailFrom: {
+     *     domain: "mail.example.com"
+     *   }
+     * }
+     * ```
+     */
+    mailFrom?: Input<{
+        /**
+         * The custom MAIL FROM subdomain. Must be a subdomain of the `sender` domain.
+         *
+         * @example
+         * ```js
+         * {
+         *   mailFrom: {
+         *     domain: "mail.example.com"
+         *   }
+         * }
+         * ```
+         */
+        domain: Input<string>;
+        /**
+         * Control what happens when the required MX record of the custom MAIL FROM domain isn't
+         * configured correctly.
+         *
+         * By default, Amazon SES falls back to using the default `amazonses.com` MAIL FROM domain.
+         * When set to `true`, Amazon SES returns a `MailFromDomainNotVerified` error instead and the
+         * emails you attempt to send from this domain are automatically rejected.
+         *
+         * @default `false`
+         * @example
+         * ```js
+         * {
+         *   mailFrom: {
+         *     domain: "mail.example.com",
+         *     rejectOnMxFailure: true
+         *   }
+         * }
+         * ```
+         */
+        rejectOnMxFailure?: Input<boolean>;
+    }>;
+    /**
+     * Configure event notifications for this Email component.
+     *
+     * @default No event notifications
+     * @example
+     *
+     * ```js
+     * {
+     *   events: {
+     *     name: "OnBounce",
+     *     types: ["bounce"],
+     *     topic: "arn:aws:sns:us-east-1:123456789012:MyTopic"
+     *   }
+     * }
+     * ```
+     */
+    events?: Input<Prettify<Events>[]>;
+    /**
+     * [Transform](/docs/components#transform) how this component creates its underlying
+     * resources.
+     */
+    transform?: {
+        /**
+         * Transform the SES identity resource.
+         */
+        identity?: Transform<sesv2.EmailIdentityArgs>;
+        /**
+         * Transform the SES configuration set resource.
+         */
+        configurationSet?: Transform<sesv2.ConfigurationSetArgs>;
+        /**
+         * Transform the SES MAIL FROM attributes resource.
+         */
+        mailFromAttributes?: Transform<sesv2.EmailIdentityMailFromAttributesArgs>;
+    };
+}
+/**
+ * The `Email` component lets you send emails in your app.
+ * It uses [Amazon Simple Email Service](https://aws.amazon.com/ses/).
+ *
+ * You can configure it to send emails from a specific email address or from any email addresses
+ * in a domain.
+ *
+ * :::tip
+ * New AWS SES accounts are in _sandbox mode_ and need to [request production access](https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html).
+ * :::
+ *
+ * By default, new AWS SES accounts are in the _sandbox mode_ and can only send
+ * email to verified email addresses and domains. It also limits your account to a sending
+ * quota. To remove these restrictions, you need to [request production access](https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html).
+ *
+ * #### Sending from an email address
+ *
+ * For using an email address as the sender, you need to verify the email address.
+ *
+ * ```ts title="sst.config.ts"
+ * const email = new sst.aws.Email("MyEmail", {
+ *   sender: "spongebob@example.com",
+ * });
+ * ```
+ *
+ * #### Sending from a domain
+ *
+ * When you use a domain as the sender, you'll need to verify that you own the domain.
+ *
+ * ```ts title="sst.config.ts"
+ * new sst.aws.Email("MyEmail", {
+ *   sender: "example.com"
+ * });
+ * ```
+ *
+ * #### Configuring DMARC
+ *
+ * ```ts title="sst.config.ts"
+ * new sst.aws.Email("MyEmail", {
+ *   sender: "example.com",
+ *   dmarc: "v=DMARC1; p=quarantine; adkim=s; aspf=s;"
+ * });
+ * ```
+ *
+ * #### Configuring a custom MAIL FROM domain
+ *
+ * ```ts title="sst.config.ts"
+ * new sst.aws.Email("MyEmail", {
+ *   sender: "example.com",
+ *   mailFrom: {
+ *     domain: "mail.example.com"
+ *   }
+ * });
+ * ```
+ *
+ * #### Link to a resource
+ *
+ * You can link it to a function or your Next.js app to send emails.
+ *
+ * ```ts {3} title="sst.config.ts"
+ * new sst.aws.Function("MyApi", {
+ *   handler: "sender.handler",
+ *   link: [email]
+ * });
+ * ```
+ *
+ * Now in your function you can use the AWS SES SDK to send emails.
+ *
+ * ```ts title="sender.ts" {1, 8}
+ * import { Resource } from "sst";
+ * import { SESv2Client, SendEmailCommand } from "@aws-sdk/client-sesv2";
+ *
+ * const client = new SESv2Client();
+ *
+ * await client.send(
+ *   new SendEmailCommand({
+ *     FromEmailAddress: Resource.MyEmail.sender,
+ *     Destination: {
+ *       ToAddresses: ["patrick@example.com"]
+ *     },
+ *     Content: {
+ *       Simple: {
+ *         Subject: { Data: "Hello World!" },
+ *         Body: { Text: { Data: "Sent from my SST app." } }
+ *       }
+ *     }
+ *   })
+ * );
+ * ```
+ */
+export declare class Email extends Component implements Link.Linkable {
+    private _sender;
+    private identity;
+    private configurationSet;
+    constructor(name: string, args: EmailArgs, opts?: ComponentResourceOptions);
+    /**
+     * The sender email address or domain name.
+     */
+    get sender(): Output<string>;
+    /**
+     * The name of the configuration set.
+     */
+    get configSet(): Output<string>;
+    /**
+     * The underlying [resources](/docs/components/#nodes) this component creates.
+     */
+    get nodes(): {
+        /**
+         * The Amazon SES identity.
+         */
+        identity: import("@pulumi/aws/sesv2/emailIdentity").EmailIdentity;
+        /**
+         * The Amazon SES configuration set.
+         */
+        configurationSet: import("@pulumi/aws/sesv2/configurationSet").ConfigurationSet;
+    };
+    /** @internal */
+    getSSTLink(): {
+        properties: {
+            sender: Output<string>;
+            configSet: Output<string>;
+        };
+        include: {
+            effect?: "allow" | "deny" | undefined;
+            actions: string[];
+            resources: Input<Input<string>[]>;
+            conditions?: Input<Input<{
+                test: Input<string>;
+                variable: Input<string>;
+                values: Input<Input<string>[]>;
+            }>[]> | undefined;
+            type: "aws.permission";
+        }[];
+    };
+    /**
+     * Reference an existing Email component with the given Amazon SES identity. This is useful
+     * when you create an SES identity in one stage and want to share it in another stage. It
+     * avoids having to create a new Email component in the other stage.
+     *
+     * @param name The name of the component.
+     * @param sender The email address or domain name of the existing SES identity.
+     * @param opts Resource options.
+     *
+     * @example
+     * Imagine you create an Email component in the `dev` stage. And in your personal stage `frank`,
+     * instead of creating a new component, you want to share the one from `dev`.
+     *
+     * ```ts title="sst.config.ts"
+     * const email = $app.stage === "frank"
+     *   ? sst.aws.Email.get("MyEmail", "spongebob@example.com")
+     *   : new sst.aws.Email("MyEmail", {
+     *       sender: "spongebob@example.com",
+     *     });
+     * ```
+     */
+    static get(name: string, sender: Input<string>, opts?: ComponentResourceOptions): Email;
+}
+export {};
+//# sourceMappingURL=email.d.ts.map

package/platform/types/components/aws/email.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"email.d.ts","sourceRoot":"","sources":["../../../../src/components/aws/email.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,wBAAwB,EACxB,MAAM,EAIP,MAAM,gBAAgB,CAAC;AACxB,OAAO,EAAE,SAAS,EAAE,QAAQ,EAAE,SAAS,EAAa,MAAM,cAAc,CAAC;AACzE,OAAO,EAAE,IAAI,EAAE,MAAM,SAAS,CAAC;AAC/B,OAAO,EAAE,KAAK,EAAE,MAAM,UAAU,CAAC;AACjC,OAAO,EAAE,GAAG,EAAE,MAAM,QAAQ,CAAC;AAE7B,OAAO,EAAwB,KAAK,EAAE,MAAM,aAAa,CAAC;AAG1D,UAAU,MAAM;IACd;;OAEG;IACH,IAAI,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;IACpB;;OAEG;IACH,KAAK,EAAE,KAAK,CACV,KAAK,CACD,MAAM,GACN,QAAQ,GACR,QAAQ,GACR,WAAW,GACX,UAAU,GACV,gBAAgB,GAChB,mBAAmB,GACnB,cAAc,GACd,MAAM,GACN,OAAO,CACV,EAAE,CACJ,CAAC;IACF;;OAEG;IACH,KAAK,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;IACtB;;OAEG;IACH,GAAG,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;CACrB;AAED,MAAM,WAAW,SAAS;IACxB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OA2CG;IACH,MAAM,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;IACtB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OA8BG;IACH,GAAG,CAAC,EAAE,KAAK,CAAC,KAAK,GAAG,CAAC,GAAG,GAAG,EAAE,CAAC,CAAC,CAAC;IAChC;;;;;;;;;;;;OAYG;IACH,KAAK,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;IACtB;;;;;;;;;;;;;;;;;;;;;;;OAuBG;IACH,QAAQ,CAAC,EAAE,KAAK,CAAC;QACf;;;;;;;;;;;WAWG;QACH,MAAM,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;QACtB;;;;;;;;;;;;;;;;;;WAkBG;QACH,iBAAiB,CAAC,EAAE,KAAK,CAAC,OAAO,CAAC,CAAC;KACpC,CAAC,CAAC;IACH;;;;;;;;;;;;;;;OAeG;IACH,MAAM,CAAC,EAAE,KAAK,CAAC,QAAQ,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;IACnC;;;OAGG;IACH,SAAS,CAAC,EAAE;QACV;;WAEG;QACH,QAAQ,CAAC,EAAE,SAAS,CAAC,KAAK,CAAC,iBAAiB,CAAC,CAAC;QAC9C;;WAEG;QACH,gBAAgB,CAAC,EAAE,SAAS,CAAC,KAAK,CAAC,oBAAoB,CAAC,CAAC;QACzD;;WAEG;QACH,kBAAkB,CAAC,EAAE,SAAS,CAAC,KAAK,CAAC,mCAAmC,CAAC,CAAC;KAC3E,CAAC;CACH;AAOD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAyFG;AACH,qBAAa,KAAM,SAAQ,SAAU,YAAW,IAAI,CAAC,QAAQ;IAC3D,OAAO,CAAC,OAAO,CAAiB;IAChC,OAAO,CAAC,QAAQ,CAAsB;IACtC,OAAO,CAAC,gBAAgB,CAAyB;gBAErC,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,SAAS,EAAE,IAAI,CAAC,EAAE,wBAAwB;IAkP1E;;OAEG;IACH,IAAW,MAAM,mBAEhB;IAED;;OAEG;IACH,IAAW,SAAS,mBAEnB;IAED;;OAEG;IACH,IAAW,KAAK;QAEZ;;WAEG;;QAEH;;WAEG;;MAGN;IAED,gBAAgB;IACT,UAAU;;;;;;;;;;;;;;;;;IAyBjB;;;;;;;;;;;;;;;;;;;;OAoBG;WACW,GAAG,CACf,IAAI,EAAE,MAAM,EACZ,MAAM,EAAE,KAAK,CAAC,MAAM,CAAC,EACrB,IAAI,CAAC,EAAE,wBAAwB;CAWlC"}