https://pulp.plan.io/https://pulp.plan.io/favicon.ico2019-06-20T13:48:28ZPulpAnsible Plugin - Issue #4996: Ansible collection remote doesn't handle trailing / in sync urlhttps://pulp.plan.io/issues/4996?journal_id=448592019-06-20T13:48:28Zbmbouterbmbouter@redhat.com
<ul><li><strong>Project</strong> changed from <i>Pulp</i> to <i>Ansible Plugin</i></li></ul><p>moving to ansible project in Redmine</p> Ansible Plugin - Issue #4996: Ansible collection remote doesn't handle trailing / in sync urlhttps://pulp.plan.io/issues/4996?journal_id=448782019-06-20T19:07:25Zsajha
<ul><li><strong>Tags</strong> <i>Katello-P3</i> added</li></ul> Ansible Plugin - Issue #4996: Ansible collection remote doesn't handle trailing / in sync urlhttps://pulp.plan.io/issues/4996?journal_id=459682019-07-23T19:29:08Zdaviddavis
<ul></ul><p>We should solve this by validating the user input and checking it ends in a <code>/</code>.</p> Ansible Plugin - Issue #4996: Ansible collection remote doesn't handle trailing / in sync urlhttps://pulp.plan.io/issues/4996?journal_id=461322019-07-30T18:43:15Zdaviddavis
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li><li><strong>Assignee</strong> set to <i>fao89</i></li><li><strong>Sprint</strong> set to <i>Sprint 56</i></li></ul> Ansible Plugin - Issue #4996: Ansible collection remote doesn't handle trailing / in sync urlhttps://pulp.plan.io/issues/4996?journal_id=461332019-07-30T18:43:25Zdaviddavis
<ul><li><strong>Triaged</strong> changed from <i>No</i> to <i>Yes</i></li></ul> Ansible Plugin - Issue #4996: Ansible collection remote doesn't handle trailing / in sync urlhttps://pulp.plan.io/issues/4996?journal_id=461512019-07-31T14:25:22Zfao89
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>POST</i></li></ul><p><a href="https://github.com/pulp/pulp_ansible/pull/147" class="external">https://github.com/pulp/pulp_ansible/pull/147</a></p> Ansible Plugin - Issue #4996: Ansible collection remote doesn't handle trailing / in sync urlhttps://pulp.plan.io/issues/4996?journal_id=461622019-07-31T16:49:44ZAnonymous
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>MODIFIED</i></li></ul><p>Applied in changeset <a class="changeset" title="validating collection remote url closes #4996" href="https://pulp.plan.io/projects/ansible_plugin/repository/pulp_ansible/revisions/28106c26cc7147cd28f92a25b0d9cedb9df3ac83">pulp_ansible|28106c26cc7147cd28f92a25b0d9cedb9df3ac83</a>.</p> Ansible Plugin - Issue #4996: Ansible collection remote doesn't handle trailing / in sync urlhttps://pulp.plan.io/issues/4996?journal_id=465432019-08-13T14:42:32Zkersom
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-5 status-13 priority-6 priority-default closed" href="/issues/5256">Test #5256</a>: Test - Ansible collection remote doesn't handle trailing / in sync url</i> added</li></ul> Ansible Plugin - Issue #4996: Ansible collection remote doesn't handle trailing / in sync urlhttps://pulp.plan.io/issues/4996?journal_id=465462019-08-13T14:43:29Zkersom
<ul><li><strong>Subject</strong> changed from <i>Asible collection remote doesn't handle trailing / in sync url</i> to <i>Ansible collection remote doesn't handle trailing / in sync url</i></li></ul> Ansible Plugin - Issue #4996: Ansible collection remote doesn't handle trailing / in sync urlhttps://pulp.plan.io/issues/4996?journal_id=471272019-08-29T13:51:29Zsajha
<ul></ul><p>This change added an error message for the trailing "/". Is there a reason we do not want to allow the trailing "/" ? We are going to handle this in our calls to pulp. However, wondering why it's not allowed..</p> Ansible Plugin - Issue #4996: Ansible collection remote doesn't handle trailing / in sync urlhttps://pulp.plan.io/issues/4996?journal_id=471282019-08-29T14:21:54Zbmbouterbmbouter@redhat.com
<ul></ul><p>Earlier in pulp_ansible sync was actually a call to the mazer client, so the URL was passed directly to mazer. If that URL contained a slash mazer would fail. This change in Pulp was a workaround to avoid this unfixed mazer issue: <a href="https://github.com/ansible/mazer/issues/288" class="external">https://github.com/ansible/mazer/issues/288</a></p>
<p>However, after this was merged, the use of mazer (and this validation workaround) were both removed as part of <a href="https://pulp.plan.io/issues/5165" class="external">https://pulp.plan.io/issues/5165</a> So in terms of the current state of the code this shouldn't be an issue. If you see any issues currently with trailing slashes please let us know.</p> Ansible Plugin - Issue #4996: Ansible collection remote doesn't handle trailing / in sync urlhttps://pulp.plan.io/issues/4996?journal_id=559882020-05-08T17:34:40Zggainey
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul> Ansible Plugin - Issue #4996: Ansible collection remote doesn't handle trailing / in sync urlhttps://pulp.plan.io/issues/4996?journal_id=560172020-05-08T17:44:11Zggainey
<ul><li><strong>Tags</strong> <i>Katello</i> added</li><li><strong>Tags</strong> deleted (<del><i>Katello-P3</i></del>)</li></ul> Ansible Plugin - Issue #4996: Ansible collection remote doesn't handle trailing / in sync urlhttps://pulp.plan.io/issues/4996?journal_id=627872020-09-23T20:01:22Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul>