aspring / racker Goto Github PK

Per https://github.com/mitchellh/packer/pull/3860/files I'm wondering how different racker is to https://github.com/ianchesal/packer-config. Any thoughts?

Thanks,
Martin.

ianchesal/packer-config#21

should the .ruby_version ship with the repo? It's specific to RVM if I recall correctly, so there's no guarantee a user has RVM, and when they do, they get a warning about not using the correct version even tho racker appears to work fine w/ruby 2.x. The gemspec specifies gem.required_ruby_version = '>= 1.9.2' so shouldn't that suffice for dictating the ruby version?

BTW, I'm a big fan of racker. Usage seems a lot more straight-forward than some of the other approaches to automating packer templates. Thanks!

I cannot get racker to output min_packer_version (and description).

Racker::Processor.register_template do |template|
  template.min_packer_version = "0.11.0"
  template.description = "my description"
end

Don't do the job. Roughly skimming rackers code I don't see how I can configure these top-level options.

My current workaround is to parse rackers output, inject the keys and output it again as JSON, but this kind of defeats the purpose of racker :)

Trying to figure out how to add run_tags to the packerized process and I don't think this script supports it. Anyone know if it does?

@aspring, I was wondering if it makes sense to add the ability of specifying which template needs to be processed before a template but within the template itself.

So that if you want to merge multiple templates like in the example:

$ racker rackertemplate1.rb rackertemplate2.rb rackertemplate3.rb packertemplate.json

You just have to specify the last one:

$ racker rackertemplate3.rb packertemplate.json

Because it already knows that depends on template 1 & 2. Or it knows that depends on template 2 and template 2 knows it depends on template 1.

Maybe a simple require_relative would do but it would be nicer if it was something more integrated into the DSL.