-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
should add extension path variables dynamically #35
Comments
assigned to @phuonglm to handle this for the related PR. |
you can create: processors/extension_path.rb to work on this and register this processor before the variables.rb processor then it should work. |
settings['variables'] should be updated to include these dynamic vars |
related: teracyhq/dev#497 If the above improvement is done, we can implement the feature of this issue on any extensions instead of waiting for teracy-dev-core. |
this should be done quickly, I guess it should not take more than 2 hours. |
You can use Util.extension_lookup_path if suitable for the lookup_path |
this can be postponed, we don't have to rush for this, so assigned to @hieptranquoc for the next sprint instead. |
this cannot be postponed, required for teracyhq-incubator/teracy-dev-v05-compat#1 |
…-to-variable-at-start should add extension path variables dynamically #35
so that extension configs should have the right path, for example, chef cookbooks_path for https://github.com/teracyhq-incubator/teracy-dev-v05-compat/pull/2/files
We should have <extension-name>-path variable so that, only enabled extensions will have the associated <extension-name>-path, the path should not include slash character (/) at the end.
should become:
By supporting this, teracyhq-incubator/teracy-dev-v05-compat#2 will not have to create a new configurator but using yaml config only.
The text was updated successfully, but these errors were encountered: