Variables in module.json

Expected Behavior

Variables should be substituted in both deployment.template.json and module.json

Current Behavior

I can set variables in .env that are used in deployment.template.json but these aren’t populated in module.json file.

We use different environments for dev and prod and hence different container registrys as well. Currently there doesn’t seem to be a way to use variables in module.json, specifically the repository value. It’d be great to use $CONTAINER_REGISTRY_SERVER in module.json as well as deployment.template.json

Similar to this, an ability for a CI system (e.g. VSTS) to set the tag version in module.json for CI/CD

e.g. module.json could look like

{
    "$schema-version": "0.0.1",
    "description": "",
    "image": {
        "repository": "$CONTAINER_REGISTRY_SERVER/myiotmodule",
        "tag": {
            "version": "$TAG_VERSION",
            "platforms": {
                "linuxx64": "./Dockerfile"
            }
        }
    },
    "language": "csharp"
}

[hubez]

Some formal docs on module.json would be nice. Might expose the various consistency issues too. I too was stumped by this and was just about to go down the path of ditching the use of module.json and iotedgedev.

[shizn]

@adashen to share the schema of module.json