Refactor (some) class-names to Apt

[m-bucher]

Should fix https://pulp.plan.io/issues/6897

Please comment about possible obstacles.

[pulpbot]

WARNING!!! This PR is not attached to an issue. In most cases this is not advisable. Please see our PR docs for more information about how to attach this PR to an issue.

[mdellweg]

I really like it, but I also do see one possible obstacle. Can you please try the migration with a seeded db. I am unsure if existing objects are properly accounted for. You might need to add a handcrafted step.

[quba42]

Since the original cause for this change, was inconsistent naming between class names, and API paths, I went and had another look at those.
This change appears to bring them exactly into line with each other. (i.e. All the things that have /apt/ in their API path are now named Apt<entity> for their class.

I wanted to draw attention one more time to the verbatim publisher since it is the other thing with an unusual name:

• API path /pulp/api/v3/publications/deb/verbatim/, class name VerbatimPublication
• API path /pulp/api/v3/publications/deb/apt/, class name AptPublication

But this now seems structurally consistent.

Also consistent when compared to pulp_file:

• API path /pulp/api/v3/publications/file/file/, class name FilePublication

[quba42]

I really like it, but I also do see one possible obstacle. Can you please try the migration with a seeded db. I am unsure if existing objects are properly accounted for. You might need to add a handcrafted step.

I am not sure if this is a meaningful test, but for what it is worth, I was still able to find everything in my source development box after applying the migration.

How else can I test this?

[quba42]

As far as I can tell the changelog entry is the only change we need...

[quba42]

@m-bucher Do we need to confirm one more time that this really does fix the original issue with the auto generated API bindings?

[m-bucher]

@quba42 I will check it out in my forklift.

[m-bucher]

@quba42 The katello-tests now no longer produce the broken URL, so I guess that is a good sign 😃

[quba42]

@mdellweg I will have one more look at a migration tomorrow, and then I would merge this.