Contents

#!/usr/bin/env ruby

example_description = <<DESC
  Sub Plans Example
  ===================

  This example shows, how to trigger the execution plans from within a
  run method of some action and waing for them to finish.

  This is useful, when doing bulk actions, where having one big
  execution plan would not be effective, or in case all the data are
  not available by the time of original action planning.

DESC

require_relative 'example_helper'
require_relative 'orchestrate_evented'

class SubPlansExample < Dynflow::Action
  include Dynflow::Action::WithSubPlans

  def create_sub_plans
    10.times.map { |i| trigger(OrchestrateEvented::CreateMachine, "host-#{i}", 'web_server') }
  end
end

if $0 == __FILE__
  triggered = ExampleHelper.world.trigger(SubPlansExample)
  puts example_description
  puts <<-MSG.gsub(/^.*\|/, '')
    |  Execution plan #{triggered.id} with sub plans triggered
    |  You can see the details at http://localhost:4567/#{triggered.id}
  MSG

  ExampleHelper.run_web_console
end

Version data entries

9 entries across 9 versions & 1 rubygems

Version	Path
dynflow-0.8.25	examples/sub_plans.rb
dynflow-0.8.24	examples/sub_plans.rb
dynflow-0.8.23	examples/sub_plans.rb
dynflow-0.8.22	examples/sub_plans.rb
dynflow-0.8.21	examples/sub_plans.rb
dynflow-0.8.20	examples/sub_plans.rb
dynflow-0.8.19	examples/sub_plans.rb
dynflow-0.8.18	examples/sub_plans.rb
dynflow-0.8.17	examples/sub_plans.rb