fix(cmd): sync needed action definitions for chosen pipeline w/ project

Author: markcda

TODO.md

@@ -30,7 +30,7 @@
   1. [x] For Pipelines
   2. [x] For containered builds & runs
   3. [x] For Ansible runs
-- [ ] Fix issue which causes not to adding actions definitions when using a pipeline from the registry, to the project config
+- [x] Fix issue which causes not to adding actions definitions when using a pipeline from the registry, to the project config
 - [x] Add `info` field to requirements to inform users about commands or links to install them
 - [x] Unify `edit`, `cat` & `rm` commands behavior
 - [x] Add possibility to setup variables inside each pipeline independently

src/pipelines.rs

@@ -437,6 +437,16 @@ impl DescribedPipeline {
 
     Ok(cmds)
   }
+
+  /// Collect needed actions (only those which are found) for running this pipeline.
+  pub fn collect_actions(&self, definitions: &BTreeSet<DefinedAction>) -> BTreeSet<DefinedAction> {
+    self
+      .actions
+      .iter()
+      .filter_map(|action| action.definition(definitions).ok())
+      .cloned()
+      .collect::<BTreeSet<_>>()
+  }
 }
 
 /// Lists all available Pipelines.
@@ -591,7 +601,7 @@ pub fn cat_project(config: &DeployerProjectOptions, args: CatProjectArgs) -> any
   Ok(())
 }
 
-/// Tries to assign and setup the Pipeline from Registry.
+/// Tries to assign and setup the pipeline from Registry.
 ///
 /// While setup, Deployer checks programming languages, target specs and
 /// deploy toolkit to make sure that Pipeline is compatible with your project.
@@ -645,6 +655,9 @@ pub fn assign_pipeline_to_project(
     DescribedPipeline::new_from_prompt(globals, &mut config.actions)?
   };
 
+  let needed_actions = pipeline.collect_actions(&globals.actions_registry);
+  config.actions = config.actions.union(&needed_actions).cloned().collect();
+
   if config.variables.is_empty() {
     println!("Please, specify variables for project first!");
     let mut needed = vec![];