Fitting directories into collection structure #299
Conversation
|
Attached issue: https://pulp.plan.io/issues/6458 |
| tags: | ||
| - pulp | ||
| - pulpcore | ||
| - content |
There was a problem hiding this comment.
Is there an approved list of what can go here? Or is it just to ease searching?
I'd add: software-repositories, lifecycle-management, content-delivery
There was a problem hiding this comment.
I'm not sure if we have an approved list, but these are good suggestions I'll add them
| # collection label 'namespace.name'. The value is a version range | ||
| # L(specifiers,https://python-semanticversion.readthedocs.io/en/latest/#requirement-specification). Multiple version | ||
| # range specifiers can be set and are separated by ',' | ||
| dependencies: {} |
There was a problem hiding this comment.
This is not the place to include the postgres role dependency?
There was a problem hiding this comment.
I'm not sure, from the autogenerated comment I understood it is for collections rather than roles, but I'm not sure!
There was a problem hiding this comment.
That's what i read, too. It seemd weird to me.
| # The URL to the collection issue tracker | ||
| issues: https://pulp.plan.io/projects/pulp/issues?query_id=156 | ||
|
|
||
| build_ignore: |
There was a problem hiding this comment.
This feature is only supported when running ansible-galaxy collection build with Ansible 2.10 or newer.
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/dev_guide/developing_collections.rst#ignoring-files-and-folders
https://pulp.plan.io/issues/6458
closes #6458