You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2016/11/29 12:49:58 UTC
[jira] [Updated] (ISIS-1503) The FixtureScripts service ought to
provide an easier mechanism to specify which user account to run the
fixtures as.
[ https://issues.apache.org/jira/browse/ISIS-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood updated ISIS-1503:
------------------------------
Fix Version/s: (was: 1.14.0)
1.13.2
> The FixtureScripts service ought to provide an easier mechanism to specify which user account to run the fixtures as.
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-1503
> URL: https://issues.apache.org/jira/browse/ISIS-1503
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.13.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: 1.13.2
>
>
> Currently fixtures are run using the "initialisation" dummy account. Although this can be explicitly overridden using the SudoService, it results in a lot of boilerplate.
> It would be nice instead if the fixture script framework (either FixtureScripts service, or ExecutionContext, or FixtureScript class) could specify the user account to use, ie call SudoService for us.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)