-
Notifications
You must be signed in to change notification settings - Fork 32
Adding a new ready condition FileState
#402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
327924d
e2558da
90ddedb
f9497c6
9f99911
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -208,6 +208,21 @@ component_properties (object) | |
| * **Allowed Values:** | ||
| * ``"Running"``: The process has started and reached its running state. | ||
| * ``"Terminated"``: The process has started, reached its running state, and then terminated successfully. | ||
| * **file_state** (object, optional) | ||
| * **Description:** Specifies a ready condition based on the existence state of a file at a given path. | ||
| * **Properties:** | ||
|
MaciejKaszynski marked this conversation as resolved.
|
||
| * **file_path** (string, required) | ||
| * **Description:** Specifies the absolute path to the file being watched. | ||
| * **state** (string, optional) | ||
| * **Description:** Specifies the required existence state of the file. | ||
| * **Allowed Values:** | ||
| * ``"Exists"``: The component is ready when the file at ``file_path`` exists. | ||
| * ``"Deleted"``: The component is ready when the file at ``file_path`` is deleted. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Are there any files which cannot be watched via inotify and thus we need to poll for their existence with some to-be-configured interval?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As discussed only containers would be problematic here, and I think for now since we do not support containers anyways I don't think we should support this yet. I think in the future we could have an optional polling_rate var that when set would switch to using polling but don't think it makes sense to pay so much of a slow down to support a very specific scenario.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree, support for polling only needs to be added if/when we support containers. |
||
| * **Default:** ``"Exists"`` | ||
| * **polling_interval** (number, optional) | ||
| * **Description:** Specifies the time interval, in seconds (e.g., ``0.5`` for 500 milliseconds), at which the **Launch Manager** checks the file existence state. | ||
| * **Constraint:** Must be greater than 0. | ||
| * **Default:** ``10ms`` | ||
|
|
||
| .. _lm_conf_deployment_config_object_: | ||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.