chore: bump kusion and kusion_models to kcl and k8s

Author: Peefy

actions

@@ -185,13 +185,13 @@
 \hspace*{1mm}\raisebox{0.5pt}{\tiny$\bullet$}~\textbf{Docker}
 
 \begin{lstlisting}
-docker pull kusionstack/kclvm
+docker pull kcllang/kcl
 \end{lstlisting}
 
 \hspace*{1mm}\raisebox{0.5pt}{\tiny$\bullet$}~\textbf{macOS}
 
 \begin{lstlisting}
-brew install kcl-lang/tap/kclvm
+brew install kcl-lang/tap/kcl
 \end{lstlisting}
 
 \hspace*{1mm}\raisebox{0.5pt}{\tiny$\bullet$}~\textbf{Linux}

cheatsheet/cheatsheet.tex

@@ -72,9 +72,9 @@ Where `{breaking_change_description}` and `{linked issue}` can be omitted if the
 For example, the commit created by Alice in branch 'alice: fix output fmt bug'.
 
 ```
-fix(kclvm-printer): fix an output format bug in kclvm-printer
+fix(kcl-printer): fix an output format bug in kcl-printer
 
-There is an output format bug in kclvm-printer because ...,
+There is an output format bug in kcl-printer because ...,
 So, The calling of method "XXX" is replaced by "HHHH"...,
 ...
 
@@ -106,7 +106,7 @@ We suggest that the PR title be consistent with the branch name and the commit m
 For example, Alice creates the PR name `fix/alice/fix_output_fmt_bug` for one branch.
 
 ```
-fix(kclvm-printer): fix an output format bug in kclvm-printer.
+fix(kcl-printer): fix an output format bug in kcl-printer.
 ```
 
 ## 5. Supported PR Types

docs/community/contribute/git-guideline.md

@@ -574,7 +574,7 @@ However, usually, the actual situation is more complicated, and the deployment m
 For example, we want to support a persistent volume claim based on an existing schema, as a reusable Kubernetes schema. In this case, we can just wrapper it with a `mixin` and a `protocol` as follows:
 
 ```python
-import kusion_kubernetes.api.core.v1
+import k8spkg.api.core.v1
 
 protocol PVCProtocol:
     pvc?: {str:}

docs/reference/lang/codelab/schema.md

@@ -1878,15 +1878,15 @@ schema Server:
     workloadType : str, default is Deployment
         Use this attribute to specify which kind of long-running service you want.
         Valid values: Deployment, CafeDeployment.
-        See also: kusion_models/core/v1/workload_metadata.k.
+        See also: k8s/core/v1/workload_metadata.k.
     name : str, default is None
         A Server-level attribute.
         The name of the long-running service.
-        See also: kusion_models/core/v1/metadata.k.
+        See also: k8s/core/v1/metadata.k.
     labels : {str:str}, optional, default is None
         A Server-level attribute.
         The labels of the long-running service.
-        See also: kusion_models/core/v1/metadata.k.
+        See also: k8s/core/v1/metadata.k.
 
     Examples
     ----------------------
@@ -2937,7 +2937,7 @@ kcl_cli_configs:
   output: ./stdout.golden
 kcl_options:
   - key: image
-    value: docker.io/kusion:latest
+    value: docker.io/kcllang/kcl:latest
 ```
 
 KCL CLI -Y parameters also support multi-file configuration, and support separate writing and merging of compilation parameters and option top level arguments parameter configuration.
@@ -2965,7 +2965,7 @@ kcl_cli_configs:
 ```yaml
 kcl_options:
   - key: image
-    value: docker.io/kusion:latest
+    value: docker.io/kcllang/kcl:latest
 ```
 
 We can use the following command line to get the meaning of each configuration parameter or see KCL Quick Start

docs/reference/lang/tour.md

@@ -14,13 +14,13 @@ Using the KCL Python plugin requires the presence of `Python 3.7+` in your `PATH
 
 ## 1. Hello Plugin
 
-KCL plugins are installed in the `plugins` subdirectory of KCL (usually installed in the `$HOME/.kusion/kclvm/plugins` directory), or set through the `$KCL_PLUGINS_ROOT` environment variable. Besides, the `plugins` directory could also be placed at the `pwd` path. KCL plugins are managed in the Git repository: [https://github.com/kcl-lang/kcl-plugin](https://github.com/kcl-lang/kcl-plugin), we can clone the repository for development.
+KCL plugins are installed in the `plugins` subdirectory of KCL (usually installed in the `$HOME/.kcl/plugins` directory), or set through the `$KCL_PLUGINS_ROOT` environment variable. Besides, the `plugins` directory could also be placed at the `pwd` path. KCL plugins are managed in the Git repository: [https://github.com/kcl-lang/kcl-plugin](https://github.com/kcl-lang/kcl-plugin), we can clone the repository for development.
 
 Enter the `kcl-plugin info` command to view the plugin directory (replace `/Users/kcl_user` with the local `$HOME` path):
 
 ```shell
 $ kcl-plugin info
-# plugin_root: /Users/kcl_user/.kusion/kclvm/plugins
+# plugin_root: /Users/kcl_user/.kcl/plugins
 ```
 
 View the list of plugins with the `kcl-plugin list` subcommand:
@@ -103,8 +103,8 @@ The information of the plugin mainly includes the name and version information o
 The directory structure of the plugin is as follows (replace `/Users/kcl_user` with the local `$HOME` path):
 
 ```shell
-$ tree /Users/kcl_user/.kusion/kclvm/plugins/
-/Users/kcl_user/.kusion/kclvm/plugins/
+$ tree /Users/kcl_user/.kcl/plugins/
+/Users/kcl_user/.kcl/plugins/
 ├── _examples
 ├── _test
 └── hello
@@ -150,14 +150,14 @@ The `kcl-plugin init` command will construct a new plugin from the built-in temp
 
 ## 6. Remove Plugin
 
-KCL plugins are located in the `plugins` subdirectory of KCL (usually installed in the `$HOME/.kusion/kclvm/plugins` directory).
+KCL plugins are located in the `plugins` subdirectory of KCL (usually installed in the `$HOME/.kcl/plugins` directory).
 We can query the plugin installation directory with the command `kcl-plugin info`.
 
 ```shell
 $ kcl-plugin info
-/Users/kcl_user/.kusion/kclvm/plugins/
-$ tree /Users/kcl_user/.kusion/kclvm/plugins/
-/Users/kcl_user/.kusion/kclvm/plugins/
+/Users/kcl_user/.kcl/plugins/
+$ tree /Users/kcl_user/.kcl/plugins/
+/Users/kcl_user/.kcl/plugins/
 ├── _examples
 ├── _test
 └── hello      -- Delete this directory to delete the hello plugin
@@ -179,7 +179,7 @@ $ kcl-plugin test hello
 platform darwin -- Python 3.7.6+, pytest-5.3.5, py-1.9.0, pluggy-0.13.1
 rootdir: /Users/kcl_user
 collected 5 items
-.kusion/kclvm/plugins/hello/plugin_test.py .....      [100%]
+.kcl/plugins/hello/plugin_test.py .....      [100%]
 ============================== 5 passed in 0.03s ===============================
 $
 ```

docs/reference/plugin/overview.md

@@ -127,15 +127,15 @@ As shown before, by default, the documentation extracted by the documentation ge
         workloadType : str, default is "Deployment", required
             Use this attribute to specify which kind of long-running service you want.
             Valid values: Deployment, CafeDeployment.
-            See also: kusion_models/core/v1/workload_metadata.k.
+            See also: k8s/core/v1/workload_metadata.k.
         name : str, required
             A Server-level attribute.
             The name of the long-running service.
-            See also: kusion_models/core/v1/metadata.k.
+            See also: k8s/core/v1/metadata.k.
         labels : {str:str}, optional
             A Server-level attribute.
             The labels of the long-running service.
-            See also: kusion_models/core/v1/metadata.k.
+            See also: k8s/core/v1/metadata.k.
 
         Examples
         ----------------------
@@ -170,7 +170,7 @@ As shown before, by default, the documentation extracted by the documentation ge
         doc: |
           Use this attribute to specify which kind of long-running service you want.
           Valid values: Deployment, CafeDeployment.
-          See also: kusion_models/core/v1/workload_metadata.k.
+          See also: k8s/core/v1/workload_metadata.k.
         type:
           type_str: str
           type_category: BUILTIN
@@ -181,7 +181,7 @@ As shown before, by default, the documentation extracted by the documentation ge
         doc: |
           A Server-level attribute.
           The name of the long-running service.
-          See also: kusion_models/core/v1/metadata.k.
+          See also: k8s/core/v1/metadata.k.
         type:
           type_str: str
           type_category: BUILTIN
@@ -192,7 +192,7 @@ As shown before, by default, the documentation extracted by the documentation ge
         doc: |
           A Server-level attribute.
           The labels of the long-running service.
-          See also: kusion_models/core/v1/metadata.k.
+          See also: k8s/core/v1/metadata.k.
         type:
           type_str: '{str: str}'
           type_category: DICT
@@ -228,7 +228,7 @@ As shown before, by default, the documentation extracted by the documentation ge
       - name: workloadType
         doc: |
           workloadType 属性定义了服务的类型，是服务级别的属性。合法的取值有：Deployment, CafeDeployment.
-          另请查看：kusion_models/core/v1/workload_metadata.k.
+          另请查看：k8s/core/v1/workload_metadata.k.
         type:
           type_str: str
           type_category: BUILTIN
@@ -238,7 +238,7 @@ As shown before, by default, the documentation extracted by the documentation ge
       - name: name
         doc: |
           name 为服务的名称，是服务级别的属性。
-          另请查看：kusion_models/core/v1/metadata.k.
+          另请查看：k8s/core/v1/metadata.k.
         type:
           type_str: str
           type_category: BUILTIN
@@ -248,7 +248,7 @@ As shown before, by default, the documentation extracted by the documentation ge
       - name: labels
         doc: |
           labels 为服务的标签，是服务级别的属性。
-          另请查看：kusion_models/core/v1/metadata.k.
+          另请查看：k8s/core/v1/metadata.k.
         type:
           type_str: '{str: str}'
           type_category: DICT
@@ -285,9 +285,9 @@ As shown before, by default, the documentation extracted by the documentation ge
   ### Attributes
   |Name and Description|Type|Default Value|Required|
   |--------------------|----|-------------|--------|
-  |**workloadType**<br />workloadType 属性定义了服务的类型，是服务级别的属性。合法的取值有：Deployment, CafeDeployment.<br />另请查看：kusion_models/core/v1/workload_metadata.k.|str|"Deployment"|**required**|
-  |**name**<br />name 为服务的名称，是服务级别的属性。<br />另请查看：kusion_models/core/v1/metadata.k.|str|Undefined|**required**|
-  |**labels**<br />labels 为服务的标签，是服务级别的属性。<br />另请查看：kusion_models/core/v1/metadata.k.|{str: str}|Undefined|optional|
+  |**workloadType**<br />workloadType 属性定义了服务的类型，是服务级别的属性。合法的取值有：Deployment, CafeDeployment.<br />另请查看：k8s/core/v1/workload_metadata.k.|str|"Deployment"|**required**|
+  |**name**<br />name 为服务的名称，是服务级别的属性。<br />另请查看：k8s/core/v1/metadata.k.|str|Undefined|**required**|
+  |**labels**<br />labels 为服务的标签，是服务级别的属性。<br />另请查看：k8s/core/v1/metadata.k.|{str: str}|Undefined|optional|
   ### Examples
   ```
   myCustomApp = AppConfiguration {

docs/tools/cli/kcl/docgen.md

@@ -1,6 +1,6 @@
 # Share Your Package
 
-[kpm](https://github.com/KusionStack/kpm) is a tool for managing kcl packages. This article will guide you on how to use kpm to push your kcl package to an OCI Registry for publication. kpm uses [ghcr.io](https://ghcr.io) as the default OCI Registry, and you can change the default OCI Registry by modifying the kpm configuration file. For information on how to modify the kpm configuration file, see [kpm oci registry](https://github.com/kcl-lang/kpm/blob/main/docs/kpm_oci.md#kpm-registry)
+[kpm](https://github.com/kcl-lang/kpm) is a tool for managing kcl packages. This article will guide you on how to use kpm to push your kcl package to an OCI Registry for publication. kpm uses [ghcr.io](https://ghcr.io) as the default OCI Registry, and you can change the default OCI Registry by modifying the kpm configuration file. For information on how to modify the kpm configuration file, see [kpm oci registry](https://github.com/kcl-lang/kpm/blob/main/docs/kpm_oci.md#kpm-registry)
 
 Here is a simple step-by-step guide on how to use kpm to push your kcl package to ghcr.io.
 

docs/user_docs/guides/package-management/4-share_your_pkg.md

@@ -2242,7 +2242,7 @@ data_type_list:
 
 ## 49. How to develop a KCL plugin?
 
-KCL plugins are installed in the plugins subdirectory of KCL (usually installed in the `$HOME/.kusion/kclvm/plugins` directory), or set through the `$KCL_PLUGINS_ROOT` environment variable. Besides, the `plugins` directory could also be placed at the `pwd` path. For plugin developers, plugins are managed in the [Git repository](https://github.com/kcl-lang/kcl-plugin), and the plugin repository can be cloned to this directory for development.
+KCL plugins are installed in the plugins subdirectory of KCL (usually installed in the `$HOME/.kcl/plugins` directory), or set through the `$KCL_PLUGINS_ROOT` environment variable. Besides, the `plugins` directory could also be placed at the `pwd` path. For plugin developers, plugins are managed in the [Git repository](https://github.com/kcl-lang/kcl-plugin), and the plugin repository can be cloned to this directory for development.
 
 KCL has built-in kcl-plugin scaffolding command to assist users to write KCL plug-ins in Python language, so that the corresponding plug-ins can be called in the KCL file to enhance the KCL language itself, such as accessing the network, reading and writing IO, CMDB query and encryption and decryption functions.
 

docs/user_docs/support/faq-kcl.md

@@ -1,5 +1,5 @@
 """
-This is the mutating_webhook module in kusion_kubernetes.api.admissionregistration.v1 package.
+This is the mutating_webhook module in k8spkg.api.admissionregistration.v1 package.
 This file was generated by the KCL auto-gen tool. DO NOT EDIT.
 Editing this file might prove futile when you re-run the KCL auto-gen generate command.
 """