[jboss-jira] [JBoss JIRA] (WFCORE-4135) Support for read only server configuration directory

Yeray Borges Santana (Jira) issues at jboss.org
Thu Mar 19 13:29:52 EDT 2020


     [ https://issues.redhat.com/browse/WFCORE-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yeray Borges Santana updated WFCORE-4135:
-----------------------------------------
    Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3531, https://github.com/wildfly/wildfly-core/pull/4104  (was: https://github.com/wildfly/wildfly-core/pull/3531)


> Support for read only server configuration directory
> ----------------------------------------------------
>
>                 Key: WFCORE-4135
>                 URL: https://issues.redhat.com/browse/WFCORE-4135
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Management
>            Reporter: Rafael Ruiz
>            Assignee: Yeray Borges Santana
>            Priority: Major
>
> -We need something like-
> ---disable-configuration-history-
> -to use when running in containers to avoid write to any directory ('standalone_xml_history').-
> History backups are senseless running on a container, and certain cloud use cases could require a non-writable storage mounted as a configuration directory. Also, when we are running on a non-containerized environment we could have very strict security rules that could force us the use of a read-only configuration directory.
> We need a solution to make the server able to work with read-only configuration directories.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the jboss-jira mailing list