[
https://issues.apache.org/jira/browse/AURORA-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047925#comment-14047925
]
Mark Chu-Carroll commented on AURORA-558:
-----------------------------------------
Pystachio *is* python. It's loaded and evaluated by the Python interpreter.
Pystachio configs are loaded as python modules. THe client gets configs out of
the .aurora files by getting a handle on the top-level dictionary associated
with the loaded module, and looking up the symbol "jobs" in it. It really is
just Python, with a nice library automatically included.
> aurora client should look for include()'ed files based on known search path
> ---------------------------------------------------------------------------
>
> Key: AURORA-558
> URL: https://issues.apache.org/jira/browse/AURORA-558
> Project: Aurora
> Issue Type: Story
> Components: Client
> Reporter: Jay Buffington
>
> We've written a standard library of sorts to be shared across our
> organization. It includes processes for doing things like downloading the
> app in a standard way, notifying a service discovery service, etc. and
> pystachio structs for things like modeling variables for our custom web
> framework.
> After a cursory glance at the code, it looks like these .aurora files have to
> be included as either an absolute path or a path relative to where the aurora
> command was run.
> When the path is relative I'd like the aurora client to first search a set of
> paths defined by an environment var like $AURORA_INC_PATH, then ./ and then a
> default set of directories that is built into the client like
> /etc/aurora/include/
--
This message was sent by Atlassian JIRA
(v6.2#6252)
