You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2015/12/28 04:07:49 UTC
[jira] [Resolved] (AURORA-915) create strict mode for .aurora
config
[ https://issues.apache.org/jira/browse/AURORA-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Farner resolved AURORA-915.
--------------------------------
Resolution: Later
I propose we table this and encourage organizations looking for enforcement of best practices to do so in other ways.
> 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)