# Galaxy importer: collection dependency handling

**URL:** <https://forum.ansible.com/t/galaxy-importer-collection-dependency-handling/3496>\
**Category:** Project Discussions\
**Tags:** vmware, dependencies, aws, collections, galaxy-ng\
**Created:** [January 27, 2024, 12:48pm UTC](https://forum.ansible.com/t/galaxy-importer-collection-dependency-handling/3496 "2024-01-27T12:48:27Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [September 22, 2025, 3:27pm UTC](https://forum.ansible.com/t/galaxy-importer-collection-dependency-handling/3496/9 "2025-09-22T15:27:48Z")

</div>

> [@tremble](#):
>
> Copying the fragments over from amazon.aws into community.aws would be problematic since the actual behaviour (including common parameters) is coming from amazon.aws and not community.aws

I’m not sure if I understand. If the actual behavior and common parameters come from amazon.aws, the docs fragments should also. This way, both would automatically be aligned.

Oh, wait! Let’s say c.a supports a.a X and later. If there’s a new a.a release Y with changes to common parameters, it’s not clear what docs fragments are the correct ones: Those from a.a X or a.a Y? After all, it depends on the a.a version people have installed. Is this what you’re meaning?

---

_[View the full topic](https://forum.ansible.com/t/galaxy-importer-collection-dependency-handling/3496)._