Azure-docs: Full documentation of YAML and JSON format

Created on 24 Aug 2018  Â·  10Comments  Â·  Source: MicrosoftDocs/azure-docs

I've seen a few examples of Service Fabric Mesh application definitions in both JSON and YAML, however I can't see to find documentation on all the various options and how to do some of the more advanced things. Are these formats documented somewhere?


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

cxp in-progress product-question service-fabric-messvc triaged

Most helpful comment

@MikeChristensen - I'm working on adding some better documentation on the options you have with YAML and JSON to describe applications correctly. This will include details on properties in resource types. If you have any specific questions in the next week or two I can definitely help out before the documentation is published - feel free to reach out to me at deep dot kapur at Microsoft dot com and we can work through setting up the template correctly. With regards to your app description above - definitely seems doable; just wanted to clarify what you mean by "resolve by hostname" for the web/api services, since in Mesh you do not have access to the host.

For the bit on app / network mapping - in the future, we will support having multiple applications in the same network, but currently, each application has its own network.

All 10 comments

Thanks for the feedback! We are currently investigating and will update you shortly.

I did a bit more digging, and it seems that YAML is just supported by the Visual Studio tools, and converted to JSON under the covers which is what the CLI tools use. So, mainly we should have good JSON documentation. Basically my app design is something like this:

  • 1 app
  • 4 services: Api, Web, Cache, Sql
  • 2 networks, each with public IP that exposes port 80

    • ApiNetwork maps port 80 to ApiService port 80

    • WebNetwork maps port 80 to WebService port 80

  • Both Web and Api can resolve Cache and Sql services by hostname

I had this working in Service Fabric, but I haven't a clue as to how to describe this with JSON, and all of the samples are just super basic examples.

@MikeChristensen thanks Mike for the extra details. Can you explain a bit more what you are looking for assistance with in the context of this doc?

I am looking for assistance writing JSON templates for Service Fabric Mesh. I can find simple examples, but I cannot find detailed documentation on network resources, service properties, etc.

Also can you clarify what _The current preview only supports a one to one mapping between applications and networks_ means?

Got it. Thanks!

@vturecek can you chime in and assist on this one?

@MikeChristensen - I'm working on adding some better documentation on the options you have with YAML and JSON to describe applications correctly. This will include details on properties in resource types. If you have any specific questions in the next week or two I can definitely help out before the documentation is published - feel free to reach out to me at deep dot kapur at Microsoft dot com and we can work through setting up the template correctly. With regards to your app description above - definitely seems doable; just wanted to clarify what you mean by "resolve by hostname" for the web/api services, since in Mesh you do not have access to the host.

For the bit on app / network mapping - in the future, we will support having multiple applications in the same network, but currently, each application has its own network.

thanks @dkkapur!

@MikeChristensen does that help?

Thanks again for helping out @dkkapur

@MikeChristensen I will close this for now but if you have additional questions just let us know :)

I would not say that this is closed, as we do not have "Service Fabric Mesh application definitions in both JSON and YAML" as originally asked for in the issue. We should reopen it!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Favna picture Favna  Â·  3Comments

behnam89 picture behnam89  Â·  3Comments

bityob picture bityob  Â·  3Comments

ianpowell2017 picture ianpowell2017  Â·  3Comments

spottedmahn picture spottedmahn  Â·  3Comments