[katello-devel] Default Custom Info for Systems

[Bryan Kearney]

On 09/25/2012 03:34 PM, Mike McCune wrote:
> On 09/25/2012 12:21 PM, Adam Price wrote:
>> hello folks!
>>
>> I just recently finished my initial custom info work for systems in
>> the api and cli. next on the docket is for organizations to set
>> default custom info keys for its systems.
>>
>> The plan is to have a list of keynames for each organization. these
>> keynames will then be placed on each system under the org with a
>> writable value (default will probably be null or empty-string).
>>
>> workflow goes like this:
>> 1. set 'asset tag' in org's default keynames
>> 2. go create a system
>> 3. 'asset tag' custom_info for system gets created
>> 4. can go back and add the value later (optional)
>>
>> here's where there is some contention:
>>
>> when a default key is specified, what should happen:
>> a. should only systems created from now-on have this default key? or
>> b. should all existing systems along with newly created systems have
>> this default key?
>
> (a)  By default it should only effect newly registered systems but we
> should offer a way with the CLI/UI to mass-apply custom info to systems.
>
> Changing that value could conceivably modify thousands of systems with a
> simple form submit.  If we do offer a way to apply this org default to
> systems within an org we should make it explicit and outside the scope
> of changing the org default a a different button and a specific API call
> and CLI command.
>
> Mike
I think all should get the key, but if that could be done in some sort 
of a lazy loading model, I think it would be great.

-- bk