)]}'
{"masakari/templates/bin/_bootstrap.sh.tpl":[{"author":{"_account_id":3009,"name":"Vladimir Kozhukalov","email":"kozhukalov@gmail.com","username":"kozhukalov"},"change_message_id":"d59d415cdc07d49bffb83341be07c2d874ca00ee","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":3,"id":"8969e658_55d30d4e","line":131,"updated":"2026-11-18 20:44:38.000000000","message":"Frankly, this script template is barely readable. I understand that you follow the practice that we already have in other charts. But this is even more convoluted and I am not sure we need to add more such things that convert complex values structures to bash code. This all now looks like the mature reconciliation and I would suggest migrating towards using CRs wherever possible. \n\nFor example, recently we introduced Keystone CRD and now the chart also deploys the minimal controller that reconciles Keystone CRs. The same approach can be used for bootstrapping services. Take a look at https://k-orc.cloud/. This is a operator for managing Openstack resources declaratively. We currently don\u0027t use it for managing keystone entities because it does not provide all the features that we need. \n\nIMO it looks like instead of using templates for generating bash code that then runs openstack commands we could just render CRs.","commit_id":"13d0c7c8b889c9b28ef66cafdc975cf04d4f875b"}]}
