Stream: IG creation
Topic: Query on package management
Brett Esler (Sep 25 2020 at 00:15):
@Grahame Grieve trying to understand an issue seen with hl7.fhir.au.base build - the Australian Digital Health Agency has a fork of AU Base where they work on changes to be later merged https://github.com/ci-collaborative/au-fhir-base-r4 whenever they commit to this repo any dependent IGs referencing current build of hl7.fhir.au.base will fetch package from http://build.fhir.org/ig/ci-collaborative/au-fhir-base-r4/ rather than /ig/hl7au/au-fhir-base - if I build hl7au again then the fetch will be from the right place.
Does the CI build end up using the location of the build to register package; I thought this was controlled by package-list.json ?
I guess if I get them to change the package id in there fork this could be avoided for now?
Grahame Grieve (Sep 25 2020 at 02:28):
#current takes the latest version of the master of the latest repo to be built. If you have 2 repos with the same package id / canonical URL, it will take which ever is built latest
Rob Eastwood (Sep 25 2020 at 06:12):
Thanks @Brett Esler and @Grahame Grieve - mmmm, I'll look at the package id idea
Rob Eastwood (Sep 28 2020 at 05:17):
Following this up earlier today with @Brett Esler to explore this further.
So, anytime that a repository fork has an update on master, the #current package is updated with the content from the fork rather than that of the "main" repository. In our case, we have a good relationship with HL7 AU in order to contribute agreed content via our fork and have strict internal processes in place to never commit our content to master. However, it would would seem possible for me to fork any IG repo, set up the autobuilder and then commit anything to my fork's master; and in so doing, the main repo's package is effectively overwritten by my update. If I have understood this correctly, that is worrying.
I wonder then, if this is a query for the autobuilder process and how packages are generated; none of which I understand. I will add a ticket on that repo to progress.
@Brett Esler or @Grahame Grieve - any thoughts?
Grahame Grieve (Sep 28 2020 at 09:54):
no this only happens on the master of the repo - it's when you have 2 different repos with the same package id
Last updated: Apr 12 2022 at 19:14 UTC
