Stream: shorthand
Topic: Applying IG publication data to resources
Elliot Silver (Aug 26 2021 at 14:56):
My search skills are failing me, but I seem to recall a discussion about applying the IG's publisher, version, copyright, etc. settings to resources within the IG. Is this something Sushi (or the publisher) does by default? I've got an IG where these seem to be propagated. I've found the documentation on apply-version, apply-copyright, apply-contact, etc. for the publisher, and from my read, the default value for all is false (don't propagate), so I'm trying to recall if this is something sushi does.
Chris Moesel (Aug 26 2021 at 16:58):
@Elliot Silver - SUSHI defaults profiles' status to active and version to the version specified in your sushi-config.yaml. SUSHI does not apply the publisher, copyright, etc. to profiles. That is something that the IG Publisher does (and as you suggested, I thought it was based on specific parameters in your IG file). You can easily see what SUSHI did or did not set by looking at the SUSHI output in fsh-generated.
Elliot Silver (Aug 26 2021 at 22:11):
First "Sushi defaults ... version to the version specified": Is that changable? If so where?
Would there be anything odd about how Sushi handles a project containing no fsh files? (It has sushi-config, and xml vocabulary, but no fsh files.)
Chris Moesel (Aug 27 2021 at 02:52):
First "Sushi defaults ... version to the version specified": Is that changable? If so where?
You can override the version for any profile via a caret rule:
* ^version = "1.2.3"
Chris Moesel (Aug 27 2021 at 02:58):
Would there be anything odd about how Sushi handles a project containing no fsh files? (It has sushi-config, and xml vocabulary, but no fsh files.)
SUSHI itself should be just fine without FSH files. It should still create the IG JSON (and menu.xml, if appropriate). BUT -- the IG Publisher only runs SUSHI if it sees an input/fsh folder. So if you don't have an input/fsh folder, then IG Publisher will not launch SUSHI. Git won't let you check in a truly empty folder, so you'd have to put an empty FSH file or text file or something in there in order for the folder to exist in Git (and then be seen by the IG Publisher in CI).
Jose Costa Teixeira (Aug 27 2021 at 07:50):
we put empty .gitignore files to keep empty folders on github
Elliot Silver (Aug 27 2021 at 16:18):
Interesting -- yeah, I came across the issue with publisher not running sushi because of the missing directory. I guess that would really be the only thing that differs; once the execution of sushi is done, I assume publisher behavior is identical regardless of whether the IG is a sushi project or not.
Chris Moesel (Aug 27 2021 at 16:44):
once the execution of sushi is done, I assume publisher behavior is identical regardless of whether the IG is a sushi project or not.
Correct. The only real difference between a SUSHI project and non-SUSHI project at that point is that the SUSHI project stores some of the sources in input/fsh-generated. But the all those sources in input basically end up getting aggregated together for the IG Publisher anyway, so it doesn't matter.
Elliot Silver (Aug 27 2021 at 19:13):
OK, I need to look at publisher behavior then. Thanks.
Last updated: Apr 12 2022 at 19:14 UTC
