-
Notifications
You must be signed in to change notification settings - Fork 756
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Importing and modifying existing Azure resources #904
Comments
Out of interest, are you able to use the ARM Export Template functionality today to fetch an ARM Template for these resources? If so, I believe that once #402 has been implemented, you should be able to fetch a template containing these resources from Azure and convert to .bicep. |
Hi, thanks for the response. It would be possible to export the resources to an ARM template and eventually convert to bicep, but I was hoping for a more «programmatic» way of achieving this. Not sure exactly what I am looking for though. 😀 |
In theory, we could add a command like: bicep export -f main.bicep --resource-id "path/to/resource" Which could do the export, convert it to bicep and add it to the file of your choosing (in this case |
Is there any progress on this idea? |
Hi,
We have a large migration project where we are using tools like Azure Migrate to migrate resources into Azure.
Azure Migrate will move and provision resources (like nics, vms and disks) outside any IaC scope.
However we would like to import/reference or somehow hook up these resources in our bicep file to start managing these through code (i.e adding a new disk). So we are looking for something similar to terraform import feature.
The text was updated successfully, but these errors were encountered: