openstack/kolla
Code Issues Proposed changes

Replace invisible unicode chars

Browse Source 
They're believed to have no special meaning and were put by accident.

TrivialFix

Change-Id: I66ea5711810ed0060cf89192a780bfcc92e79770
(cherry picked from commit 2ddf0aeb20)
This commit is contained in:
Piotr Parczewski 2023-03-28 14:08:42 +02:00 committed by Michal Nasiadka
parent 9516d00f3b
commit 59dd65a99b
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docker/base/Dockerfile.j2
View File

@ -139,9 +139,9 @@ RUN rm -f /etc/rpm/macros.image-language-conf \
{%- if not loop.last %} \{% endif %} {%- if not loop.last %} \{% endif %}
{% endfor -%} {% endfor -%}
{% for cmd in rpm_setup %} {% for cmd in rpm_setup %}
{{ cmd }} {{ cmd }}
{% endfor %} {% endfor %}
{% block base_centos_repo_overrides_post_rpm %}{% endblock %} {% block base_centos_repo_overrides_post_rpm %}{% endblock %}

2
specs/logging-with-heka.rst
View File

@ -256,7 +256,7 @@ An alternative to this proposal involves using Logstash in a centralized
way as done in [1]. way as done in [1].
Another alternative would be to execute Logstash on each cluster node, as this Another alternative would be to execute Logstash on each cluster node, as this
spec proposes with Heka. But this would mean running a JVM on each cluster spec proposes with Heka. But this would mean running a JVM on each cluster
node, and using Redis as a centralized queue. node, and using Redis as a centralized queue.
Also, as described above, we initially considered relying on services writing Also, as described above, we initially considered relying on services writing