Add configuration option for appending to sys.path #179
Conversation
|
Thanks @troyready - can you add this to the config docs? |
|
i have the same layout for my configs with the following I then just install them with:
|
|
I don't have a preference though, if this is easier for people, I'm fine with adding it to the config. |
|
@phobologic I've added documentation for the new option, should be ready for review again @mhahn thanks for the background -- I totally hadn't seen that issue. Would be nice to include it in the docs somehow; not sure where the best spot would be |
| Module Paths | ||
| ---------------- | ||
| When setting the ``classpath`` for blueprints/hooks, it is sometimes desirable to | ||
| load modules from outside the default ```sys.path`` (e.g., to include modules |
There was a problem hiding this comment.
nit: one too many backticks at the beginning of sys.path. Also, is the backtick syntax valid for RST?
There was a problem hiding this comment.
@phobologic good catch, should be fixed now.
rst is new to me, so I was using the syntax from their doc site
This gives the ability to load hooks & blueprints from arbitrary local paths. E.g., ``` $ cat conf/config.yaml sys_path: ./ stacks: - name: bastion ... ``` With this set, blueprints/hooks can be kept in the same repo as the configuration files.
|
Cool - looks good. Thanks @troyready ! |
I'd like to be able to store my configs and blueprints in the same repository, e.g.:
Currently this isn't possible because util/load_object_from_string only loads from the default
sys.pathwhich doesn't include the top level repo directory (only the system paths and the stacker directory under its pip installed location ofsrc/stacker/.With this commit the yaml configuration file can optionally include a top-level
sys_pathkey which will append its value tosys.path, e.g.sys_path: ./.