[
https://issues.apache.org/jira/browse/IGNITE-15047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-15047:
-----------------------------------
Description:
In order to provide consistent update of configuration and metastorage metadata
we should have configuration values that are hidden form the user.
Requirements are:
* these configuration values should be available from internal code only
* they should not be accessible in JSON or any other configuration view
representation
* they can't be updated via CLI's HOCON update requests or any other public
API calls
One possible solution is to have configuration schema extensions, registered in
"internal" modules - they'll lead to generation of extended VIEW and CHANGE
interfaces. All extra fields from these schemas will be marked as internal by
configuration framework, technically it is possible.
h3. API notes
was:
In order to provide consistent update of configuration and metastorage metadata
we should have configuration values that are hidden form the user.
Requirements are:
* these configuration values should be available from internal code only
* they should not be accessible in JSON or any other configuration view
representation
* they can't be updated via CLI's HOCON update requests or any other public
API calls
One possible solution is to have configuration schema extensions, registered in
"internal" modules - they'll lead to generation of extended VIEW and CHANGE
interfaces. All extra fields from these schemas will be marked as internal by
configuration framework, technically it is possible.
> Support internal/private properties in configuration framework
> --------------------------------------------------------------
>
> Key: IGNITE-15047
> URL: https://issues.apache.org/jira/browse/IGNITE-15047
> Project: Ignite
> Issue Type: Task
> Reporter: Ivan Bessonov
> Priority: Major
> Labels: iep-55, ignite-3
>
> In order to provide consistent update of configuration and metastorage
> metadata we should have configuration values that are hidden form the user.
> Requirements are:
> * these configuration values should be available from internal code only
> * they should not be accessible in JSON or any other configuration view
> representation
> * they can't be updated via CLI's HOCON update requests or any other public
> API calls
> One possible solution is to have configuration schema extensions, registered
> in "internal" modules - they'll lead to generation of extended VIEW and
> CHANGE interfaces. All extra fields from these schemas will be marked as
> internal by configuration framework, technically it is possible.
> h3. API notes
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
