<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla-ansible.git/tools/generate_passwords.py, branch stable/2026.1</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.platform-os.org/openstack/kolla-ansible.git/atom?h=stable%2F2026.1</id>
<link rel='self' href='https://git.platform-os.org/openstack/kolla-ansible.git/atom?h=stable%2F2026.1'/>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/'/>
<updated>2017-02-15T08:34:51+00:00</updated>
<entry>
<title>Rename kolla namespace to kolla_ansible</title>
<updated>2017-02-15T08:34:51+00:00</updated>
<author>
<name>Jeffrey Zhang</name>
<email>zhang.lei.fly@gmail.com</email>
</author>
<published>2017-02-15T03:51:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=177fbea79a1babdcd4e8230341380d373eef6df4'/>
<id>urn:sha1:177fbea79a1babdcd4e8230341380d373eef6df4</id>
<content type='text'>
* Rename kolla namespace to kolla_ansible
* remove oslo.config.opts entry points which is uesless
* delete useless tools/version-check.py script

Change-Id: I005dd7223ff23afbb2ce8cbfd0ebec0969102798
</content>
</entry>
<entry>
<title>Add generate_passwords.py to generate passwords</title>
<updated>2016-03-21T17:02:23+00:00</updated>
<author>
<name>SamYaple</name>
<email>sam@yaple.net</email>
</author>
<published>2016-03-16T21:45:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=f03e06e09bc486a1a26d5642cce278d7dbb7bd92'/>
<id>urn:sha1:f03e06e09bc486a1a26d5642cce278d7dbb7bd92</id>
<content type='text'>
As with all tools, this is a first pass at the generation. Perhaps we
even want to move this into kolla/kolla/cmd and be generated with tox
itself in the future.

This tool, when run, will only populate empty fields that have no
values meaning that it is safe to run repeatedly on the same file.

Of note, there is no way to preserve comments in the file after it has
been processed by the yaml parser in python. Comments and sections
will remain in the passwords.yml template for additional documentation
if the user wishes to populate the file themselves.

Use SystemRandom and clean up the docs a bit to not use pronouns.

Co-Authored-By: Steven Dake &lt;stdake@cisco.com&gt;

Closes-Bug: #1559266
Change-Id: I2932d592df8871f1b7811059206d0b4d0553a687
</content>
</entry>
</feed>
