locked
ARM Deployment Issues RRS feed

  • Question

  • Hi,

    I have  Generated the Templates using the below

    https://github.com/MLogdberg/APIManagementARMTemplateCreator

    it got successfully generated.

    I have around 5 APIS which consists of 15 operations and a ton of policies

    I have used a single ARM Template for the entire Artifacts. So the ARM Template is around 6 MB.

    when i deploy this i faced  issues like below

      "code": "ValidationError",
        "message": "One or more fields contain incorrect values:",
        "details": [
          {
            "code": "ValidationError",
            "target": "aid",
            "message": "API not found"
          }

    this is happening when the product is getting associated with API

    when i run the same script second time, it doesn't have a problem.

    this is happening because API Creation and the Product assicateion might be happening simultanesly.

    Since the API is huge its taking time. is there a way we can add delay or make it wait until the creation of API?

    Thanks,

    Sujith.



    Sujith

    Friday, August 30, 2019 9:07 AM

Answers

  • Hello Sujith,

    Resource Manager evaluates the dependencies between resources, and deploys them in their dependent order. When resources aren't dependent on each other, Resource Manager deploys them in parallel. You only need to define dependencies for resources that are deployed in the same template. If the resources you are deploying having a dependency with each other you should use dependsOn  element Within your template, the dependsOn element enables you to define one resource as a dependent on one or more resources.

    https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-define-dependencies

    Friday, August 30, 2019 10:39 AM

All replies

  • Hello Sujith,

    Resource Manager evaluates the dependencies between resources, and deploys them in their dependent order. When resources aren't dependent on each other, Resource Manager deploys them in parallel. You only need to define dependencies for resources that are deployed in the same template. If the resources you are deploying having a dependency with each other you should use dependsOn  element Within your template, the dependsOn element enables you to define one resource as a dependent on one or more resources.

    https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-define-dependencies

    Friday, August 30, 2019 10:39 AM
  • Thanks Ketan  i think i can solve it now

    Sujith

    Friday, August 30, 2019 11:28 AM