entrypoint -> path

Signed-off-by: Abhishek Kumar <[email protected]>

Author: shwstppr

source/adminguide/extensions.rst

@@ -37,18 +37,18 @@ Configuration
 
 Administrators can define and manage the following components of an extension:
 
-   - Entry Point: A file or script that will be executed during extension operations.
+   - Path: A path to a file or script that will be executed during extension operations.
 
    - Configuration Details: Key-value properties used by the extension at runtime.
 
    - Resource Mappings: Association between extensions and CloudStack resources such as clusters, etc.
 
-Entry Point
-^^^^^^^^^^^
+Path and Availabilty
+^^^^^^^^^^^^^^^^^^^^
 
-The entry point for an extension can be any binary or executable script. If no explicit entry point is provided, CloudStack uses a default base Bash script. The state of the entry point is validated across all management servers. In the UI, the Entry Point State is displayed as Not Ready if the file is missing, inaccessible, or differs across management servers.
+The path for an extension can point to any binary or executable script. If no explicit path is provided, CloudStack uses a default base Bash script. The state of the path is validated across all management servers. In the UI, the Availabilty is displayed as Not Ready if the file is missing, inaccessible, or differs across management servers.
 
-All extension entry point files are stored under a directory named after the extension within `/usr/share/cloudstack-management/extensions`.
+All extension files are stored under a directory named after the extension within `/usr/share/cloudstack-management/extensions`.
 
 Payload
 ^^^^^^^

source/adminguide/extensions/custom_actions.rst

@@ -17,7 +17,7 @@
 Custom Actions
 --------------
 
-In addition to standard instance operations, extensions support custom actions. These can be configured via UI in the extension details view or the addCustomAction API. The extension entry-point must implement handlers for these action names and process any provided parameters.
+In addition to standard instance operations, extensions support custom actions. These can be configured via UI in the extension details view or the addCustomAction API. The extension binary or script must implement handlers for these action names and process any provided parameters.
 
    |add-custom-action.png|
 
@@ -30,7 +30,7 @@ Success and error messages will be used and returned during action execution. Th
    - {{resourceName}} for showing name of the resource
 
 An example usage can be - "Successfully completed {{actionName}} for {{resourceName}} using {{extensionName}}".
-Configuration details can be key-value pairs which will be passed to the extension entry-point during action execution.
+Configuration details can be key-value pairs which will be passed to the extension during action execution.
 Timeout value can be configured to adjust wait time for action completion.
 
 A single parameter can have the following details:

source/adminguide/extensions/troubleshooting.rst

@@ -17,22 +17,22 @@
 Troubleshooting Extensions
 --------------------------
 
-Validate the Extension Entry Point
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Validate the Extension Path
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-   - Ensure that the entry point path is correctly defined and accessible on all management servers.
+   - Ensure that the path is correctly defined and accessible on all management servers.
 
    - The script or binary must be executable and have appropriate permissions.
 
    - If the binary differs across management servers, the extension will be marked as Not Ready.
 
-   - Entry points are stored at: `/usr/share/cloudstack-management/extensions/<extension_name>`
+   - Ensure files are stored at: `/usr/share/cloudstack-management/extensions/<extension_name>`
 
-   - CloudStack runs a background task at regular intervals to verify entry point readiness. If the entry point is not ready, its state will appear as Not Ready in the UI or API responses.
+   - CloudStack runs a background task at regular intervals to verify path readiness. If the path is not ready, its state will appear as Not Ready in the UI or API responses.
 
-   - Alerts are generated if an entry point is not ready.
+   - Alerts are generated if the extension path is not ready.
 
-   - The check interval can be configured using the cloudstack.extensions.entrypoint.check.interval property in global.properties. The default is 5 minutes.
+   - The check interval can be configured using the global configuration - `extension.path.state.check.interval`. The default is 5 minutes.
 
 Verify Payload Handling
 ^^^^^^^^^^^^^^^^^^^^^^^