Pulp

Today

• 
  gmbnomis Pulp

  01:17 PM · Commented on issue

  bmbouter wrote:
  > We have several plugin writer conventions about which python modules they will place various objects. We could do one more of those and have the plugin writer write a MyPluginRepositoryVersionHandler. This would be in ... Issue #3541: Core should not add/remove content to a repository or create a repository_version wi...

  General Problem:
  Some plugins have validation requirements for the membership of content units in a repository. The validation required depends on the plugin and the content type. Currently add/remove is done with a POST to v3/rep...

10/15/2019

• 
  gmbnomis Pulp

  12:03 AM · Created issue

  Issue #5574 (NEW): Provide an easy to use way to ensure the ref_name attribute convention

  Due to issue #5562, pulpcore_plugin proposes a convention for the @ref_name@ attribute of serializer @Meta@ classes.
  Ideally, all serializers defined by plugins would use this convention automatically. That seems hard to achieve, sinc...

10/14/2019

• 
  gmbnomis Pulp

  10:32 PM · Commented on issue

  I am very sorry to be late again with my comment, but, looking at the current proposal, it feels very much like a distributed implementation of a plugin specific add/remove endpoint (the former option 1). What I mean by this: If we impl... Issue #3541: Core should not add/remove content to a repository or create a repository_version wi...

  General Problem:
  Some plugins have validation requirements for the membership of content units in a repository. The validation required depends on the plugin and the content type. Currently add/remove is done with a POST to v3/rep...

10/12/2019

• 
  gmbnomis Pulp

  06:38 PM · Commented on issue

  Another option for where to implement it:
  Given we have #3541, we could offer the entire @repo_key@ check as a generic implementation that plugins may mix in/derive from/use in their @add_content@ hooks.
  This would simplify the @a... Issue #5567: Content with duplicate repo_keys can be added to a repo version

  Steps to reproduce:
  1. Create two files with the same relative_path
  2. Add them to a repository with one single call
  You'll end up with both in the repository, which is not valid. The problem is that the code is not checking the s...
• 
  gmbnomis Pulp

  06:17 PM · Commented on issue

  I think we are trying to make a rather "esoteric" use case work if we map file/directory name conflicts to @index@ or @.default@ or similar.
  What should happen if there is already a file/directory named @index@ or @.default@? We are ... Story #5559: As a plugin writer, I cannot export my Publication to POSIX filesystems

  Say you create a Publication with 3 PublishedMetadata objects, each with an Artifact to be served to the user for that relative_path. Note ...

10/10/2019

• 
  gmbnomis Pulp

  09:05 PM · Commented on issue

  I agree, I think @add_content@ should validate its input. Issue #5567: Content with duplicate repo_keys can be added to a repo version

  Steps to reproduce:
  1. Create two files with the same relative_path
  2. Add them to a repository with one single call
  You'll end up with both in the repository, which is not valid. The problem is that the code is not checking the s...

10/05/2019

• 
  gmbnomis Pulp

  11:10 PM · Committed changeset

  Add "--fail" parameter to the invocation of curl.
  [noissue] Revision b80b2343 (plugin_template): Fail if the doc build can't get the api.json schema from Pulp
• 
  gmbnomis Pulp

  10:56 PM · Committed changeset

  If a plugin uses a serializer with a HiddenField, the generator
  crashed because it did not expect a None value for a field.
  Fix this by catching the None case.
  [noissue] Revision 7366dcec (pulpcore): Fix open API generator crash on hidden field

09/28/2019

• 
  gmbnomis Pulp

  07:36 PM · Committed changeset

  When building a release on a tag, the Travis build should ensure that the
  plugin works with released versions of the pulpcore and pulpcore-plugin
  modules. This should catch issues like https://pulp.plan.io/issues/5509.
  If the Travis bui... Revision 3b819afc (plugin_template): Travis: Build on tag uses PyPI modules

09/26/2019

• 
  gmbnomis Pulp

  11:59 PM · Commented on issue

  bmbouter wrote:
  > Actually this got me thinking that in cases where 404 is returned, it could fallback to a lazy config for that content unit and continue. This would give more reliability when content remotes are unreliable. Is this be... Story #5286: As a user, a Remote should provide an option that allows download errors, e.g. 404 e...

  Problem
  If you sync a file repository where one of the files is missing, it seems that the repository syncs as much as it can (as expected), but its reported as a fatal error, with a state of 'failed'.
  This is especially proble...