Merge pull request #610 from entando/ENDOC-595

ENDOC-595 update ent app and ent pod info
entando · Oct 31, 2022 · 1074346 · 1074346
2 parents 104f6c1 + 7ecc766
commit 1074346
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/vuepress/docs/next/docs/getting-started/ent-diag.md b/vuepress/docs/next/docs/getting-started/ent-diag.md
@@ -12,16 +12,16 @@ Diagnostic information is critical to analysis and troubleshooting, and the Enta
 | `ent bundle info` |Show status information for the bundle project|
 | `ent --debug bundle "command"` |Enable debug mode|
 | `ent diag` | Run diagnostics on the pods currently in an Entando namespace and prepare a diagnostic tar.gz
-| `ent pod-info` | Display the output of `kubectl describe` and `kubectl logs` for each Entando pod in a namespace
+| `ent pod "command"` | Displays information related to a set of pods
 | `ent pod grep --all "error\|fail"` | Locate error messages within EntandoApp pods 
 
-
 ### Command Details
-* `ent diag`: Executes operations to analyze, organize and output detailed pod information. In addition to calling `ent pod-info`, `ent diag` exports custom resources, ingresses, deployments, "previous" pod logs, namespace events, etc. It also generates diagnostics and returns log paths similar to the following:
+* `ent diag`: Executes operations to analyze, organize and output detailed pod information. It exports custom resources, ingresses, deployments, "previous" pod logs, namespace events, etc. The command also generates diagnostics and returns log paths like the following:
    ```
    > Collected diagdata available under "~/.entando/reports/entando-diagdata-2020-11-19T02:58:47+0000" for consultation
    > Collected diagdata available in archive "~/.entando/reports/entando-diagdata-2020-11-19T02:58:47+0000.tgz"
    ```
+* `ent pod "command"`: Analyzes pods in a cluster with commands like `describe`, `logs`, `shell`, `force-reload`, `port-forward`, and others.  
 
 ### Log Files
 Log files for the `ent bundle build` and `pack` commands are generated for each component inside the .entando/logs directory. For single components and other processes, they are printed to the standard outputs.
diff --git a/vuepress/docs/v7.1/docs/getting-started/ent-diag.md b/vuepress/docs/v7.1/docs/getting-started/ent-diag.md
@@ -12,16 +12,16 @@ Diagnostic information is critical to analysis and troubleshooting, and the Enta
 | `ent bundle info` |Show status information for the bundle project|
 | `ent --debug bundle "command"` |Enable debug mode|
 | `ent diag` | Run diagnostics on the pods currently in an Entando namespace and prepare a diagnostic tar.gz
-| `ent pod-info` | Display the output of `kubectl describe` and `kubectl logs` for each Entando pod in a namespace
+| `ent pod "command"` | Displays information related to a set of pods
 | `ent pod grep --all "error\|fail"` | Locate error messages within EntandoApp pods 
 
-
 ### Command Details
-* `ent diag`: Executes operations to analyze, organize and output detailed pod information. In addition to calling `ent pod-info`, `ent diag` exports custom resources, ingresses, deployments, "previous" pod logs, namespace events, etc. It also generates diagnostics and returns log paths similar to the following:
+* `ent diag`: Executes operations to analyze, organize and output detailed pod information. It exports custom resources, ingresses, deployments, "previous" pod logs, namespace events, etc. The command also generates diagnostics and returns log paths like the following:
    ```
    > Collected diagdata available under "~/.entando/reports/entando-diagdata-2020-11-19T02:58:47+0000" for consultation
    > Collected diagdata available in archive "~/.entando/reports/entando-diagdata-2020-11-19T02:58:47+0000.tgz"
    ```
+* `ent pod "command"`: Analyzes pods in a cluster with commands like `describe`, `logs`, `shell`, `force-reload`, `port-forward`, and others. 
 
 ### Log Files
 Log files for the `ent bundle build` and `pack` commands are generated for each component inside the .entando/logs directory. For single components and other processes, they are printed to the standard outputs.