We can leave it how it is, and see how it feels when we are using it.


On Mon, May 5, 2014 at 3:03 PM, Kevin Gilpin <kevin.gilpin@alum.mit.edu>wrote:

> I'm not too worried about bloat, since each directory can contain its own
> .conjurrc which will merge with the ~/.conjurrc
>
>
> On Mon, May 5, 2014 at 2:44 PM, hleb-rubanau <notifications@github.com>wrote:
>
>> In lib/conjur/command/env.rb:
>>
>> > +    environments.each { |e|
>> > +      contents = api.environment(e).attributes["variables"]
>> > +      contents.each { |k,v| vars[k]=v }
>> > +    }
>> > +    return vars
>> > +  end
>> > +
>> > +  arg_name "-- command [arg1, arg2 ...] "
>> > +  Conjur::CLI.command :env do |c|
>> > +    c.desc "Environment configuration file"
>> > +    c.default_value '.conjurenv'
>> > +    c.flag ["f", "file"]
>> > +
>> > +    c.action do |global_options,options,args|
>> > +
>> > +      filename=options[:file] || '.conjurenv'
>>
>> I am not sure it is a good idea.
>>
>> .conjurrc defines general parameters of client connection, and generally
>> does not contain any information about Conjur contents (variables, users,
>> etc.)
>>
>> This file specifies bundle of variables, which can vary significantly
>> between invocations. On the other hand, it does not care about endpoints,
>> etc.
>>
>> I do not think that mixing "connection context" and "environment context"
>> in single file will be convenient, as well as bloating .conjurrc with all
>> possible bundles of variables (that will happen in case of Jenkins)
>>
>> —
>> Reply to this email directly or view it on GitHub<https://github.com/conjurinc/cli-ruby/pull/37/files#r12292870>
>> .
>>
>
>