feat: update spec

withfig-bot · Sep 17, 2024 · eab253c · eab253c
1 parent 1fe8e7a
commit eab253c
Show file tree

Hide file tree

Showing 61 changed files with 6,496 additions and 694 deletions.
diff --git a/src/aws.ts b/src/aws.ts
diff --git a/src/aws/amplify.ts b/src/aws/amplify.ts
@@ -359,7 +359,7 @@ const completionSpec: Fig.Spec = {
         {
           name: "--platform",
           description:
-            "The platform for the Amplify app. For a static app, set the platform type to WEB. For a dynamic server-side rendered (SSR) app, set the platform type to WEB_COMPUTE. For an app requiring Amplify Hosting's original SSR support only, set the platform type to WEB_DYNAMIC",
+            "The platform for the Amplify app. For a static app, set the platform type to WEB. For a dynamic server-side rendered (SSR) app, set the platform type to WEB_COMPUTE. For an app requiring Amplify Hosting's original SSR support only, set the platform type to WEB_DYNAMIC. If you are deploying an SSG only app with Next.js version 14 or later, you must set the platform type to WEB_COMPUTE and set the artifacts baseDirectory to .next in the application's build settings. For an example of the build specification settings, see Amplify build settings for a Next.js 14 SSG application in the Amplify Hosting User Guide",
           args: {
             name: "string",
             suggestions: ["WEB"],
@@ -2282,7 +2282,7 @@ const completionSpec: Fig.Spec = {
         {
           name: "--platform",
           description:
-            "The platform for the Amplify app. For a static app, set the platform type to WEB. For a dynamic server-side rendered (SSR) app, set the platform type to WEB_COMPUTE. For an app requiring Amplify Hosting's original SSR support only, set the platform type to WEB_DYNAMIC",
+            "The platform for the Amplify app. For a static app, set the platform type to WEB. For a dynamic server-side rendered (SSR) app, set the platform type to WEB_COMPUTE. For an app requiring Amplify Hosting's original SSR support only, set the platform type to WEB_DYNAMIC. If you are deploying an SSG only app with Next.js version 14 or later, you must set the platform type to WEB_COMPUTE",
           args: {
             name: "string",
             suggestions: ["WEB"],

diff --git a/src/aws/appconfig.ts b/src/aws/appconfig.ts
@@ -424,7 +424,7 @@ const completionSpec: Fig.Spec = {
     {
       name: "create-hosted-configuration-version",
       description:
-        "Creates a new configuration in the AppConfig hosted configuration store",
+        "Creates a new configuration in the AppConfig hosted configuration store. If you're creating a feature flag, we recommend you familiarize yourself with the JSON schema for feature flag data. For more information, see Type reference for AWS.AppConfig.FeatureFlags in the AppConfig User Guide",
       options: [
         {
           name: "--application-id",
@@ -450,7 +450,7 @@ const completionSpec: Fig.Spec = {
         {
           name: "--content",
           description:
-            "The content of the configuration or the configuration data",
+            "The configuration data, as bytes.  AppConfig accepts any type of data, including text formats like JSON or TOML, or binary formats like protocol buffers or compressed data",
           args: {
             name: "blob",
           },
@@ -490,8 +490,7 @@ const completionSpec: Fig.Spec = {
     },
     {
       name: "delete-application",
-      description:
-        "Deletes an application. Deleting an application does not delete a configuration from a host",
+      description: "Deletes an application",
       options: [
         {
           name: "--application-id",
@@ -522,7 +521,7 @@ const completionSpec: Fig.Spec = {
     {
       name: "delete-configuration-profile",
       description:
-        "Deletes a configuration profile. Deleting a configuration profile does not delete a configuration from a host",
+        "Deletes a configuration profile. To prevent users from unintentionally deleting actively-used configuration profiles, enable deletion protection",
       options: [
         {
           name: "--application-id",
@@ -539,6 +538,14 @@ const completionSpec: Fig.Spec = {
             name: "string",
           },
         },
+        {
+          name: "--deletion-protection-check",
+          description:
+            "A parameter to configure deletion protection. If enabled, deletion protection prevents a user from deleting a configuration profile if your application has called either GetLatestConfiguration or for the configuration profile during the specified interval.  This parameter supports the following values:    BYPASS: Instructs AppConfig to bypass the deletion protection check and delete a configuration profile even if deletion protection would have otherwise prevented it.     APPLY: Instructs the deletion protection check to run, even if deletion protection is disabled at the account level. APPLY also forces the deletion protection check to run against resources created in the past hour, which are normally excluded from deletion protection checks.     ACCOUNT_DEFAULT: The default setting, which instructs AppConfig to implement the deletion protection value specified in the UpdateAccountSettings API",
+          args: {
+            name: "string",
+          },
+        },
         {
           name: "--cli-input-json",
           description:
@@ -560,8 +567,7 @@ const completionSpec: Fig.Spec = {
     },
     {
       name: "delete-deployment-strategy",
-      description:
-        "Deletes a deployment strategy. Deleting a deployment strategy does not delete a configuration from a host",
+      description: "Deletes a deployment strategy",
       options: [
         {
           name: "--deployment-strategy-id",
@@ -592,8 +598,15 @@ const completionSpec: Fig.Spec = {
     {
       name: "delete-environment",
       description:
-        "Deletes an environment. Deleting an environment does not delete a configuration from a host",
+        "Deletes an environment. To prevent users from unintentionally deleting actively-used environments, enable deletion protection",
       options: [
+        {
+          name: "--environment-id",
+          description: "The ID of the environment that you want to delete",
+          args: {
+            name: "string",
+          },
+        },
         {
           name: "--application-id",
           description:
@@ -603,8 +616,9 @@ const completionSpec: Fig.Spec = {
           },
         },
         {
-          name: "--environment-id",
-          description: "The ID of the environment that you want to delete",
+          name: "--deletion-protection-check",
+          description:
+            "A parameter to configure deletion protection. If enabled, deletion protection prevents a user from deleting an environment if your application called either GetLatestConfiguration or in the environment during the specified interval.  This parameter supports the following values:    BYPASS: Instructs AppConfig to bypass the deletion protection check and delete a configuration profile even if deletion protection would have otherwise prevented it.     APPLY: Instructs the deletion protection check to run, even if deletion protection is disabled at the account level. APPLY also forces the deletion protection check to run against resources created in the past hour, which are normally excluded from deletion protection checks.     ACCOUNT_DEFAULT: The default setting, which instructs AppConfig to implement the deletion protection value specified in the UpdateAccountSettings API",
           args: {
             name: "string",
           },
@@ -744,6 +758,30 @@ const completionSpec: Fig.Spec = {
         },
       ],
     },
+    {
+      name: "get-account-settings",
+      description:
+        "Returns information about the status of the DeletionProtection parameter",
+      options: [
+        {
+          name: "--cli-input-json",
+          description:
+            "Performs service operation based on the JSON string provided. The JSON string follows the format provided by ``--generate-cli-skeleton``. If other arguments are provided on the command line, the CLI values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally",
+          args: {
+            name: "string",
+          },
+        },
+        {
+          name: "--generate-cli-skeleton",
+          description:
+            "Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value ``input``, prints a sample input JSON that can be used as an argument for ``--cli-input-json``. If provided with the value ``output``, it validates the command inputs and returns a sample output JSON for that command",
+          args: {
+            name: "string",
+            suggestions: ["input", "output"],
+          },
+        },
+      ],
+    },
     {
       name: "get-application",
       description: "Retrieves information about an application",
@@ -1927,6 +1965,37 @@ const completionSpec: Fig.Spec = {
         },
       ],
     },
+    {
+      name: "update-account-settings",
+      description: "Updates the value of the DeletionProtection parameter",
+      options: [
+        {
+          name: "--deletion-protection",
+          description:
+            "A parameter to configure deletion protection. If enabled, deletion protection prevents a user from deleting a configuration profile or an environment if AppConfig has called either GetLatestConfiguration or for the configuration profile or from the environment during the specified interval. Deletion protection is disabled by default. The default interval for ProtectionPeriodInMinutes is 60",
+          args: {
+            name: "structure",
+          },
+        },
+        {
+          name: "--cli-input-json",
+          description:
+            "Performs service operation based on the JSON string provided. The JSON string follows the format provided by ``--generate-cli-skeleton``. If other arguments are provided on the command line, the CLI values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally",
+          args: {
+            name: "string",
+          },
+        },
+        {
+          name: "--generate-cli-skeleton",
+          description:
+            "Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value ``input``, prints a sample input JSON that can be used as an argument for ``--cli-input-json``. If provided with the value ``output``, it validates the command inputs and returns a sample output JSON for that command",
+          args: {
+            name: "string",
+            suggestions: ["input", "output"],
+          },
+        },
+      ],
+    },
     {
       name: "update-application",
       description: "Updates an application",