Fix include files in Storage Integration articles

[alistairmatthews]

Summary

The include file storage-bicep.md was referenced in both parent articles and in storage-app-host.md causing a long section of content to be repeated in all three Storage Integration articles. I've removed the reference to it from storage-app-host.md.

Fixes #4236

[IEvangelist]

I think the best fix is to remove the bicep include from the parent articles and let the shared apphost include MD, be the only to reference the include.

Something like this:

• Parent.md
  • AppHost.include
    • Bicep.include
• SomeOtherParent.md
  • AppHost.include
    • Bicep.include

Does that make sense?

[alistairmatthews]

Yeah, I considered that, but I think in that case, the content appears in the wrong place - immediately after "Adding a Storage Resource" you get a long section on Bicep, before returning to "Connect to an existing Azure Storage account", "Add Azure Storage emulator resource" and so on.

In my view, the article should cover all the ways of adding storage resources, then adding a queue resource (or whatever storage service you want), then customizing the Bicep. In which case the include has to be referenced from the three parent files.

WDYT? Happy to be overruled!

[IEvangelist]

Yeah, I considered that, but I think in that case, the content appears in the wrong place - immediately after "Adding a Storage Resource" you get a long section on Bicep, before returning to "Connect to an existing Azure Storage account", "Add Azure Storage emulator resource" and so on.

In my view, the article should cover all the ways of adding storage resources, then adding a queue resource (or whatever storage service you want), then customizing the Bicep. In which case the include has to be referenced from the three parent files.

WDYT? Happy to be overruled!

I tend to agree with you. Right now, the issue is that all the other Azure content follows this same ordering, so we've kind of set an expectation. If you're up to it, you could move all the other bicep/provisioning includes out of their respective app host includes and into the parent articles. That would improve the flow of them all, it's just a bit of busy work.

[alistairmatthews]

Yeah, I considered that, but I think in that case, the content appears in the wrong place - immediately after "Adding a Storage Resource" you get a long section on Bicep, before returning to "Connect to an existing Azure Storage account", "Add Azure Storage emulator resource" and so on.
In my view, the article should cover all the ways of adding storage resources, then adding a queue resource (or whatever storage service you want), then customizing the Bicep. In which case the include has to be referenced from the three parent files.
WDYT? Happy to be overruled!

I tend to agree with you. Right now, the issue is that all the other Azure content follows this same ordering, so we've kind of set an expectation. If you're up to it, you could move all the other bicep/provisioning includes out of their respective app host includes and into the parent articles. That would improve the flow of them all, it's just a bit of busy work.

No problem. I'll do that in a separate issue/PR.