You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Alejandro Fernandez (JIRA)" <ji...@apache.org> on 2016/07/15 20:43:20 UTC
[jira] [Created] (AMBARI-17745) Disallow {{variable}} in configs
that load variables from python files since very error-prone and not
maintainable
Alejandro Fernandez created AMBARI-17745:
--------------------------------------------
Summary: Disallow {{variable}} in configs that load variables from python files since very error-prone and not maintainable
Key: AMBARI-17745
URL: https://issues.apache.org/jira/browse/AMBARI-17745
Project: Ambari
Issue Type: Story
Components: stacks
Affects Versions: 2.4.0
Reporter: Alejandro Fernandez
Fix For: trunk
Today, we allow configs to contain values like {{variable}} that are interpreted by loading variables from params.py, params_linux.py, or status_params.py
This type of code is very dangerous because if the config gets saved in the DB, and then the user upgrades the stack or changes the value, or Ambari modifies the variable name, then it will be broken.
The fact that python code cannot then rename a variable is an extremely poor design choice.
We should remove the dynamic interpretation of {{python_variable}}.
We only need to be able to read from other configs saved in the DB.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)