-
Notifications
You must be signed in to change notification settings - Fork 55
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
feat: Invoking a sub-command from an operation workflow #2792
feat: Invoking a sub-command from an operation workflow #2792
Conversation
Robot Results
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files
|
tests/RobotFramework/tests/tedge_agent/workflows/restart_sub_command.toml
Outdated
Show resolved
Hide resolved
/// A set of values to be injected/extracted into/from a [GenericCommandState] | ||
#[derive(Clone, Debug, Deserialize, Eq, PartialEq)] | ||
#[serde(try_from = "Option<Value>")] | ||
pub enum StateExcerpt { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some unit tests for the conversions to/from this struct would be good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You seem to have missed this. Can be added in a follow-up PR as well, to avoid blocking this one.
Signed-off-by: Didier Wenzek <[email protected]>
- A super-command can trigger a sub-command defined by another workflow - Data can be injected from the current super-command state payload into the sub-command init payload. - Data can be injected back from the successful sub-command payload into the super-command current state payload. Signed-off-by: Didier Wenzek <[email protected]>
AwaitHandlers will also be used to await the completion of a subcommand. Signed-off-by: Didier Wenzek <[email protected]>
Signed-off-by: Didier Wenzek <[email protected]>
Extracting a value from a command state will be required for the next which is to extract data from a command state and to inject this excerpt into a sub-command state. Signed-off-by: Didier Wenzek <[email protected]>
Signed-off-by: Didier Wenzek <[email protected]>
Signed-off-by: Didier Wenzek <[email protected]>
Signed-off-by: Didier Wenzek <[email protected]>
Signed-off-by: Didier Wenzek <[email protected]>
Signed-off-by: Didier Wenzek <[email protected]>
…kflow The word *command* is easily confused with *script*. Signed-off-by: Didier Wenzek <[email protected]>
Signed-off-by: Didier Wenzek <[email protected]>
Signed-off-by: Didier Wenzek <[email protected]>
Signed-off-by: Didier Wenzek <[email protected]>
… payload Signed-off-by: Didier Wenzek <[email protected]>
Signed-off-by: Didier Wenzek <[email protected]>
Signed-off-by: Didier Wenzek <[email protected]>
Signed-off-by: Reuben Miller <[email protected]>
Signed-off-by: Reuben Miller <[email protected]>
Signed-off-by: Reuben Miller <[email protected]>
Signed-off-by: Reuben Miller <[email protected]>
d6aef9a
to
25ca6e6
Compare
Proposed changes
Types of changes
Paste Link to the issue
Checklist
cargo fmt
as mentioned in CODING_GUIDELINEScargo clippy
as mentioned in CODING_GUIDELINESFurther comments
Follow-up tasks
await_operation_completion
steps.