Skip to content
This repository has been archived by the owner on Dec 6, 2023. It is now read-only.

Build resource group #15

Open
sanchetanparmar opened this issue Dec 17, 2019 · 4 comments
Open

Build resource group #15

sanchetanparmar opened this issue Dec 17, 2019 · 4 comments
Labels
enhancement New feature or request

Comments

@sanchetanparmar
Copy link

Due to limited permission, can't create new Resource group while building image.
how can use - build_resource_group_name as we can use in packer ?

@danielsollondon
Copy link
Owner

Hi - unfortunately image builder can only create a resource group currently, we have it on the backlog to make this option available to customers. One option, you could use Image Builder in silo'd subscription, and share the image to the other subscription using the Azure Shared Image Gallery.

@sanchetanparmar
Copy link
Author

sanchetanparmar commented Dec 17, 2019

HI, thanks for response. Other subscription won't help. if you have any work around please share.
@danielsollondon In this case i need SPN, has permission to create new resource group. right ?

@danielsollondon danielsollondon added the help wanted Extra attention is needed label Jan 23, 2020
@danielsollondon danielsollondon added enhancement New feature or request and removed help wanted Extra attention is needed labels Apr 30, 2020
@danielsollondon
Copy link
Owner

We are looking to allow customers to specify an existing RG, ETA end of Summer 2020, stay tuned.

If you are blocked creating the image builder staging resource group due to existing Azure Policy, one option is to ask you admins for an exception for testing only, in a test subscription with allowing IT_* resource groups, something like the below. Please do not just apply this example policy below in any environment, it is for illustration, and any changes must be tested thoroughly, and validated with your security and compliance teams.

{
"mode": "Indexed",
"parameters": {},
"policyRule": {
"if": {
"allOf": [
{
"field": "name",
"notEquals": "[resourceGroup().name]"
},
{
"field": "name",
"notContains": "IT_"
}
]
},
"then": {
"effect": "deny"
}
}
}

@danielsollondon
Copy link
Owner

This is something we still have on our backlog, but are delayed, we will have clearer dates in 2nd half of 2021.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants