FHIR Chat · IG configuration after sushi update · shorthand

Stream: shorthand

Topic: IG configuration after sushi update

Giorgio Cangioli (Jun 15 2020 at 14:37):

I'm using FSH in my IGs for rapid prototyping some of the used resources, but not for developing the whole IG.
After the last sushi update I recompiled my IG, and now only fsh specified resources are rendered (e.g. no logical models) and also the specialized template I created is no more used (the IG uses now the basic purple template).

What I need to configure (and how) to come back to the previous status ?

Chris Moesel (Jun 15 2020 at 14:59):

Hi @Giorgio Cangioli. In theory, the SUSHI 0.13.x releases should produce an initial config.yaml file that produces the same output as SUSHI 0.12.7. It sounds like your experience is different than that. I'd like to understand why.

• Did you edit config.yaml after SUSHI 0.13.x created it?
• Did you delete ig-data or any files in ig-data since upgrading to 0.13.x
• Does the config.yaml file have FSHOnly set? If so, to what?

If this is a public project, please send us the GitHub URL and we can take a look.

If you need to roll back to SUSHI 0.12.x, you can run npm install -g fsh-sushi@0.12.7 -- but we would still appreciate your help in identifying what's wrong with 0.13.x so we can fix it!

Giorgio Cangioli (Jun 15 2020 at 15:13):

Chris Moesel said:

• Did you edit config.yaml after SUSHI 0.13.x created it?

I opened the file, but I've not seen anything to modify..

Giorgio Cangioli (Jun 15 2020 at 15:18):

Chris Moesel said:

• Did you delete ig-data or any files in ig-data since upgrading to 0.13.x

I had no ig-data folder; I added an empty folder to by-pass the sushi error.
Should I remove it ?

Giorgio Cangioli (Jun 15 2020 at 15:21):

Chris Moesel said:

• Does the config.yaml file have FSHOnly set? If so, to what?

I don't see any FSHOnly label.. is this what you are asking for ?

Chris Moesel (Jun 15 2020 at 15:29):

I had no ig-data folder; I added an empty folder to by-pass the sushi error.

If you did not have ig-data, where did you have your ig.ini w/ local template, logical models, etc? In the same location as SUSHI uses for its output folder? If so, SUSHI might have overwritten them (or some of them) when you ran SUSHI?

If you don't want SUSHI to create the IG stuff, the config.yaml should have this:

FSHOnly: true

I thought SUSHI would add that to config.yaml for you if you did not have an ig-data folder when it ran the first time. We'll check on that. For now, try adding that and see if it helps. You also may need to manually revert some of the other IG-specific files if SUSHI overwrote them.

Giorgio Cangioli (Jun 15 2020 at 15:32):

thank you Chris. I'll try and let you know.

Chris Moesel (Jun 15 2020 at 15:36):

Also, w/ SUSHI 0.13.1 released this morning, the ig-data folder bug is fixed, so you can delete that now anyway.

Giorgio Cangioli (Jun 15 2020 at 15:42):

:tada: .. it seems the issue was the absence of "FSHOnly: true". :thank_you:

Chris Moesel (Jun 15 2020 at 15:44):

Great. And we've just confirmed that SUSHI is not setting that property correctly when it generates a new config.yaml. So thanks for reporting this. We'll work on fixing that so others don't run into the same issue as you did.

Chris Moesel (Jun 15 2020 at 18:45):

@Giorgio Cangioli -- it's a little too late to help you (at least on that one project), but we've fixed the config.yaml generation bug so that future users will have FSHOnly set correctly depending on their existing project. It's in the new SUSHI 0.13.2 release. Thanks again for helping us find this one!

Last updated: Apr 12 2022 at 19:14 UTC