<p>George Joseph <strong>uploaded patch set #2</strong> to this change.</p><p><a href="https://gerrit.asterisk.org/c/testsuite/+/16563">View Change</a></p><pre style="font-family: monospace,monospace; white-space: pre-wrap;">testsuite: Allow copying of arbitrary files to asterisk instances<br><br>If you have a key or certificate file that has to go in<br>/var/lib/asterisk/keys, there was no way for a test to get<br>that file into that directory. Various work-arounds ensued.<br><br>* Added automatic installation of files in a test's "files"<br> directory to its Asterisk instance's well-known directories.<br> To use, create directories named after entries in the<br> asterisk.conf "directories" category and place your files there.<br> It works much like the test's "configs" directory.<br><br> For example:<br> mytest/<br> configs/<br> ast1/<br> someconfig.conf<br> ast2/<br> someconfig.conf<br> files/<br> common/<br> astvarlibdir/<br> keys/<br> ca.crt<br> ast1/<br> astvarlibdir/<br> keys/<br> mykey1.pem<br> ast2/<br> astvarlibdir/<br> keys/<br> mykey2.pem<br> test-config.yaml<br><br> Since 'astvarlibdir' is usually defined in asterisk.conf as<br> '/var/lib/asterisk', this would copy 'ca.crt' to both Asterisk<br> instance's '/var/lib/asterisk/keys' directory, 'mykey1.pem' to<br> the first Asterisk instance's '/var/lib/asterisk/keys' directory<br> and 'mykey2.pem' to the second instance's '/var/lib/asterisk/keys'<br> directory.<br><br> Each of the instance's "someconfig.conf" could reference those<br> files like so:<br><br> cacert = <<astvarlibdir>>/keys/ca.crt.pem<br> keyfile = <<astvarlibdir>>/keys/mykeyN.pem<br><br> If you have files that can be shared among tests, you can define<br> 'base-files-path' in each test's 'test-object-config' section which<br> would point to a directory structured like the 'files' directory<br> above.<br><br> For example<br> mytests/<br> myfiles/<br> common/<br> astvarlibdir/<br> keys/<br> ca.crt<br> ast1/<br> astvarlibdir/<br> keys/<br> mykey1.pem<br> ast2/<br> astvarlibdir/<br> keys/<br> mykey2.pem<br><br> mytest1/<br> ...<br> mytest2/<br> ...<br><br> Then in both test's test-config.yaml...<br> test-object-config:<br> base-files-path: 'tests/mytests/myfiles'<br><br> base-files-path is processed before the automatic files<br> processing of each test so individual tests can add its own files<br> or even override a common file if it chooses.<br><br>ASTERISK-29675<br><br>Change-Id: I69bb54fea459e83f65a474d3b74c40b28fe01b4c<br>---<br>M README.txt<br>M lib/python/asterisk/asterisk.py<br>M lib/python/asterisk/test_case.py<br>A lib/python/polyfill.py<br>M sample-yaml/test-config.yaml.sample<br>5 files changed, 218 insertions(+), 2 deletions(-)<br><br></pre><pre style="font-family: monospace,monospace; white-space: pre-wrap;">git pull ssh://gerrit.asterisk.org:29418/testsuite refs/changes/63/16563/2</pre><p>To view, visit <a href="https://gerrit.asterisk.org/c/testsuite/+/16563">change 16563</a>. To unsubscribe, or for help writing mail filters, visit <a href="https://gerrit.asterisk.org/settings">settings</a>.</p><div itemscope itemtype="http://schema.org/EmailMessage"><div itemscope itemprop="action" itemtype="http://schema.org/ViewAction"><link itemprop="url" href="https://gerrit.asterisk.org/c/testsuite/+/16563"/><meta itemprop="name" content="View Change"/></div></div>
<div style="display:none"> Gerrit-Project: testsuite </div>
<div style="display:none"> Gerrit-Branch: 16 </div>
<div style="display:none"> Gerrit-Change-Id: I69bb54fea459e83f65a474d3b74c40b28fe01b4c </div>
<div style="display:none"> Gerrit-Change-Number: 16563 </div>
<div style="display:none"> Gerrit-PatchSet: 2 </div>
<div style="display:none"> Gerrit-Owner: George Joseph <gjoseph@digium.com> </div>
<div style="display:none"> Gerrit-CC: Friendly Automation </div>
<div style="display:none"> Gerrit-MessageType: newpatchset </div>