aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua Cohen (JIRA)" <>
Subject [jira] [Commented] (AURORA-915) create strict mode for .aurora config
Date Mon, 01 Dec 2014 23:24:12 GMT


Joshua Cohen commented on AURORA-915:

[~wickman] How do you feel about allowing configs to explicitly enable (or disable) strict
mode? That would allow people currently writing configs that rely upon features that would
no longer be available under strict mode to get their configs in order rather than dropping
a world-breaking change on them.

Perhaps a comment at the top of the config like {{# no strict}}. Or maybe even {{# strict
= warn}} or some such, so they could see the strict mode problems and address them or file
tickets to get support added for their use cases (i.e. we've already identified \\{{system.user}}
as something to add, there are likely to be other cases that will be discovered as well).

> create strict mode for .aurora config
> -------------------------------------
>                 Key: AURORA-915
>                 URL:
>             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

View raw message