Jon

My feedback

  1. 1,699 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    175 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jon commented  · 

    devils advocate here...

    If they do this, they need to come up with an actual 'id' that is not dependent on the resource group name. TONS of work and re-referencing...

    Should have done it right the first time around...check out AWS as a reference. (ie dont create an id that is contingent on another resource)

  2. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Jon supported this idea  · 
  3. 8 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Jon supported this idea  · 
    An error occurred while saving the comment
    Jon commented  · 

    Better yet it makes WAY more sense to add this information in the 'resources' key of the JSON, rather than properties.

    Jon shared this idea  · 

Feedback and Knowledge Base