Seeing the same for ks_meta: not being rendered/available when using
$ks_meta
but each individual parameter defined via ks_meta are being available
($my_var1, $my_var2.
mgmt_parameters is being rendered (and seems to include the ks_meta):
so that $mgmt_parameters is expanded to a json struct containing what you
might be looking for Plus some additional fields like tree and from_cobbler.
just add this in your ks_templete
# A_TEST = $ks_meta
# ANOTHER = $mgmt_parameters
# ANOTHER ONE = $from_cobbler and $tree and $my_var1
expanded as below (some value replaced with <skipped>):
# A_TEST = $ks_meta
# ANOTHER = {'my_var1': '2017.07.1', 'tree': '<skipped>',
'from_cobbler': 1, 'my_var2': 'a_value', 'partnumber': 'NONE'}
# ANOTHER ONE = $from_cobbler and <skipped> and 2017.07.1
So if you now the name of the variables passed via ks_meta this is easy job
else you need to parse the json from $mgmt_parameters to extract the values
you need,
2017-08-24 19:11 GMT+02:00 Michael C. Tiernan <[email protected]>:
> So I have taken to including a section in my kickstart that reads the
> values of the ks_meta parameter and the value of mgmt_parameters.
>
> It seems that while ks_meta, is defined by cobbler (seen from dumpvars) it
> does not seem to be showing up in my cheetah/kickstart environment.
>
> Two questions.
>
> 1) Anyone else seen this?
>
> 2) Is there a way to do a dumpvars type of listing of existing variables
> from inside the cheetah code?
>
> Thanks for all your time.
> _______________________________________________
> cobbler mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
cobbler mailing list -- [email protected]
To unsubscribe send an email to [email protected]
