You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Bryan Rosander (JIRA)" <ji...@apache.org> on 2019/03/12 16:24:00 UTC
[jira] [Updated] (NIFIREG-236) External configuration of docker
container
[ https://issues.apache.org/jira/browse/NIFIREG-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Rosander updated NIFIREG-236:
-----------------------------------
Description:
In some environments (e.g. Kubernetes, docker-compose, etc) it is convenient to supply configuration files externally.
In these deployment scenarios having immutable, easy to reason about configuration is desirable.
To this end, we should be able to tell the registry's start.sh not to apply any changes to config files.
was:
In some environments (e.g. Kubernetes, docker-compose, etc) it is convenient to supply configuration files externally.
In these deployment scenarios, having immutable, easy to reason about configuration is desirable.
To this end, we should be able to tell the registry's start.sh not to apply any changes to config files.
> External configuration of docker container
> ------------------------------------------
>
> Key: NIFIREG-236
> URL: https://issues.apache.org/jira/browse/NIFIREG-236
> Project: NiFi Registry
> Issue Type: New Feature
> Reporter: Bryan Rosander
> Priority: Major
>
> In some environments (e.g. Kubernetes, docker-compose, etc) it is convenient to supply configuration files externally.
> In these deployment scenarios having immutable, easy to reason about configuration is desirable.
> To this end, we should be able to tell the registry's start.sh not to apply any changes to config files.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)