Skip to content

Need a way to pass options into the livery script #47

Closed
rtyler opened this Issue Aug 12, 2012 · 2 comments

1 participant

@rtyler
Owner
rtyler commented Aug 12, 2012

For puppet specifically, being able to overwrite the manifest file and the module path would be handy

@rtyler rtyler was assigned Aug 12, 2012
@rtyler
Owner
rtyler commented Aug 22, 2012

Starting work on this now.

(This message brought to you by Hub board)

@rtyler
Owner
rtyler commented Aug 25, 2012

The "spec" I'm looking at for doing this is something along these lines:

        Blimpy.fleet do |f|
          f.add(:aws) do |ship|
            ship.name = 'cucumber-livery'
            ship.livery = Blimpy::Livery::Puppet.configure do |p|
              p.module_path = './modules'
              p.manifest_path = './test/site.pp'
              p.options = '--verbose'
            end
          end
        end

This should allow each livery to easily support its own liveries and make it such that you can pull in external liveries with a require statement easily

@rtyler rtyler added a commit that closed this issue Aug 25, 2012
@rtyler Add a new built-in (and configurable) Puppet livery.
This will allow for easier bootstrapping and configuration of Puppet on a
machine, e.g.:

    Blimpy.fleet do |f|
      f.add(:aws) do |s|
        s.livery = Blimpy::Livery::Puppet.configure |c|
          c.module_path = "test/modules" # This is relative to the Blimpfile's root directory
        end
      end
    end

In a way, this should fix #47
0ad9815
@rtyler rtyler closed this in 0ad9815 Aug 25, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.