search

uvsmtid / common-salt-states

A framework of interrelated states and pillars on top of Saltstack common to other projects.
Apache License 2.0
2 stars 0 forks source link

Use command line parameters to dynamically provide values for bootstrap package generation #27

Closed uvsmtid closed 8 years ago

uvsmtid commented 8 years ago

If pillars still need to contain information about target profile name, path to directory with pillars, etc., it is more convenient to use command line parameters (i.g. parameter pillars for state.sls function) to make this data available because bootstrap package generation process is a single-shot execution which does not need to be constantly changed and committed in revisioned files.

In other words, it should be IMpossible to grep target profile name in pillar files belonging to source profile - this is simply not checked in.

uvsmtid commented 8 years ago

This probably makes issue #13 degenerate into simply having no keys like *bootstrap_target_env* at all. Does it?

In fact, the target profile name is not required even in argument. The target profile just that (constantly) - "the target profile" (the pillar files pointed by static symlink to Git repository checked out at specific branch with pillar files for target environment).

uvsmtid commented 8 years ago

Currently, script generate_bootstrap_package.sh passes required profile name as pillar= argument for state.sls function, but will change (see #31 - due to the removal of target pillar profile configuration from pillars) to check out required branch instead (see also #29).

uvsmtid commented 8 years ago

It's done.

Commit a30bd34404869e5510d5311f3fdf440f56d91975 remove any mentioning of bootstrap target profile name inside pillars and fixed generate_bootstrap_package.sh script to get bootstrap target profile name as argument on the command line (to be used as branch name to checkout relevant pillars repository branch).

uvsmtid commented 8 years ago

Cross-reference to umbrella task #8.