search

Azure / service-fabric-mesh-preview

Service Fabric Mesh is the Service Fabric's serverless offering to enable developers to deploy containerized applications without managing infrastructure. Service Fabric Mesh , aka project “SeaBreeze” is currently available in private preview. This repository will be used for tracking bugs/feature requests as GitHub issues and for maintaining the latest documentation.
MIT License
82 stars 12 forks source link

Allow Azure parameters to be defined in template file #25

Open jjcollinge opened 6 years ago

jjcollinge commented 6 years ago

I'm not sure how feasible this is, but I can imagine in the future, configs being generated dynamically using templating languages etc. To make this simple - it'd be useful to be able (optional) to define all the config in the template file - including the Azure specific bits i.e.

{
    "name": "generatedCgsName",
    "resource_group": "generatedRgName",
    "location": "West Europe",
    "instanceCount": 2,
    "containerGroup": {
        ...

This could then be deployed x-platform using: az sbz cgs create --template-file .\generatedConfig.json You'd then also have a single deployment artifact rather than a file and a command to inspect in automated CI/CD pipelines.

mattrowmsft commented 6 years ago

I think our changes slated for preview 2 will address this nicely. Stay tuned.

mattrowmsft commented 6 years ago

@jjcollinge I'm wondering how close to what you were wanting we ended up getting. The visual studio yaml files end up getting translated for local/azure deployment. Certainly on azure with ARM templates you can do most of this customization.