Migration Plugin

Hello,

I've got a Foreman/Katello installation and recently migrated all the repos to Pulp3. During that, the SLES repos got successfully migrated, but the sles_auth_token was not set.

In Pulp2, the auth token could be set by specifying it as a query parameter as part of the url. This seems to cause the Pulp 2to3 Migration plugin to treat the auth_token as part of the URL and just keep the token as is.

Example:

Given we have a Pulp2 remote with the following URL:

https://updates.suse.com/SUSE/Products/SLE-Module-Legacy/12/x86_64/product/?abc-i-removed-the-auth-token-manually

Then the resulting Pulp 3 remote then looks like this:

{
  "pulp_href": "/pulp/api/v3/remotes/rpm/rpm/e11dc866-b38c-43a1-85ce-3c378bf12198/",
  "pulp_created": "2021-08-14T13:33:37.551888Z",
  "name": "5ea944d18a0c8441a6fcaac4-db9d7b99-f62d-499e-b2ff-297db52a32ad",
  "url": "https://updates.suse.com/SUSE/Products/SLE-Module-Legacy/12/x86_64/product/?abc-i-removed-the-auth-token-manually",
  "ca_cert": null,
  "client_cert": null,
  "client_key": null,
  "tls_validation": true,
  "proxy_url": "http://proxy.example.com:8000",
  "username": null,
  "password": null,
  "pulp_last_updated": "2021-08-14T13:33:37.551923Z",
  "download_concurrency": 20,
  "policy": "immediate",
  "sles_auth_token": null
}

You might find more information here (Foreman plugin used to manage SLES repositories): https://github.com/ATIX-AG/foreman_scc_manager/issues/43

This seems to be related to: https://pulp.plan.io/issues/6927