[
https://issues.apache.org/jira/browse/AURORA-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072816#comment-15072816
]
Joshua Cohen commented on AURORA-915:
-------------------------------------
Encouraging organizations to do this in other ways essentially means
encouraging organizations to maintain a fork or to build a complex system to
pre-process configs. I understand that we want to remain focused on the
essentials, but I'm not sure where the harm is in leaving more aspirational
tickets open?
> create strict mode for .aurora config
> -------------------------------------
>
> Key: AURORA-915
> URL: https://issues.apache.org/jira/browse/AURORA-915
> Project: Aurora
> Issue Type: Task
> Components: Client
> Reporter: brian wickman
>
> I propose we have a strict mode for .aurora configuration (pystachio) that
> prevents importing python modules (including os and sys.) Possibly we
> snapshot os.environ and provide a binding helper to give access to it. For
> people who need things like the current user, perhaps provide a default
> binding like {{\{\{system.user\}\}}} and the like. We are getting bitten by
> people adding too much sophistication into .aurora configuration like full
> blown sys.args introspection and web clients, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
