Skip to content
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

Support for built-in variables #48

Open
GoogleCodeExporter opened this issue Mar 13, 2015 · 3 comments
Open

Support for built-in variables #48

GoogleCodeExporter opened this issue Mar 13, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

Hi!

You will find a doc file where I try to explain my problem.

Original issue reported on code.google.com by [email protected] on 18 Jun 2012 at 8:32

Attachments:

@GoogleCodeExporter
Copy link
Author

Title should read: support for user variables. Built-in variables are to some 
extent supported.

Original comment by roland.bouman on 18 Jun 2012 at 11:02

@joaociocca
Copy link
Contributor

from what I understand about the cookbook process, it just reads the jobs and transformations XML files, it won't execute, interpret or replace user variables - and I doubt it really should, actually...

@rpbouman
Copy link
Owner

rpbouman commented Nov 5, 2015

Yeah it's a tough nut. One the one hand it is useful to replace some built-in variables - for example, I usually use job dir, trans dir and so on to keep related transformations and jobs together. I'd really like that to be picked up and documented all after expanding those vars.

But user vars are functional elements that can help make a job / transformation dynamic. If you push another value into those, you don't suddenly get a new job or trans that needs to be documented; rather, I would want to document the fact that a variable is used, not what people put into that variable.

Keeping the issue open in case someone else has thoughts on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants