Handle heroku addons

Still a wip, but I want to give it some visibility
I like that naming convention better. HerokuManager makes sense as the main abstract manager since Dynosaur in its current state will never be used for anything outside of Heroku.


--

Daniel Schwartz

HARRY'S

Mobile: 914.400.7609



Like: Facebook / Follow: @harrys

On Wed, Oct 29, 2014 at 12:38 PM, Pierre <notifications@github.com> wrote:

>> +        (input_plugins_config || []).each do |input_plugin_config|
>> +          @input_plugins << load_input_plugin(input_plugin_config)
>> +        end
>> +      end
>> +
>> +      def load_input_plugin(input_plugin_config)
>> +        # Load the class and instanciate it
>> +        begin
>> +          klass = Kernel.const_get(input_plugin_config['type'])
>> +          return klass.new(input_plugin_config)
>> +        rescue NameError => e
>> +          raise "Could not load #{input_plugin_config['type']}, #{e.message}"
>> +        end
>> +      end
>> +
>> +      def heroku_manager
> definitely, I was thinking that Heroku manger would handle everything, but that would be better to have a `HerokuDynoManager`, and `HerokuAddonManager` for each addon
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/harrystech/dynosaur/pull/4/files#r19551576