There is still a fair amount of code that implements various part of support for loading collection archives 'collection archive' meaning tar.gz files that are not 'artifacts' and are not built by 'mazer build'. This type of 'collection archive' is just a tar.gz that includes the content of a collection (in particular, as generated by githubs archive creation API's like those that created the tar.gz files of ansible roles installed with galaxy).
Since galaxy will stop supporting the import of collection via it's github repo (ie, the way traditional roles are imported into galaxy) there is no need to support this format any more. The only archive format supported in the future will be the collection artifact style.
Removing this code will help simplify some of the archive loading and install pathways, as well as some of the finicky archive type detection and handling code used when installing a local archive file from the cli .
alikins
commented
5 years ago
There is still a fair amount of code that implements various part of support for loading collection archives 'collection archive' meaning tar.gz files that are not 'artifacts' and are not built by 'mazer build'. This type of 'collection archive' is just a tar.gz that includes the content of a collection (in particular, as generated by githubs archive creation API's like those that created the tar.gz files of ansible roles installed with galaxy).
Since galaxy will stop supporting the import of collection via it's github repo (ie, the way traditional roles are imported into galaxy) there is no need to support this format any more. The only archive format supported in the future will be the collection artifact style.
Removing this code will help simplify some of the archive loading and install pathways, as well as some of the finicky archive type detection and handling code used when installing a local archive file from the cli .