You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Nikolay Izhikov (Jira)" <ji...@apache.org> on 2021/04/19 11:03:00 UTC

[jira] [Updated] (IGNITE-14592) Incapsulate config modification logic into callback

     [ https://issues.apache.org/jira/browse/IGNITE-14592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nikolay Izhikov updated IGNITE-14592:
-------------------------------------
    Description: 
Currently, {{ignite_aware.py}} contains several pieces of code for config modification based on some external parameters(update_ssl_config_from_globals, _prepare_configs).
This modifications should be placed in single config callback.

  was:
Right now extensions of {{IgniteSpec}} can't provide custom config files and it's templates because only template returned from spec if {{IgniteConfigTemplate}}.

We need to return array of tuples from {{IgniteSpec#config_templates}} that specify config files required to be generated to run Ignite based node.


> Incapsulate config modification logic into callback
> ---------------------------------------------------
>
>                 Key: IGNITE-14592
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14592
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Nikolay Izhikov
>            Assignee: Nikolay Izhikov
>            Priority: Major
>
> Currently, {{ignite_aware.py}} contains several pieces of code for config modification based on some external parameters(update_ssl_config_from_globals, _prepare_configs).
> This modifications should be placed in single config callback.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)