Skip to content

Feature Request: Az Snapshot Copy #559

Closed

Description

Extension name (the extension in question)

image-copy-extension

Description of issue (in as much detail as possible)

Currently, 'Specialized' osStates aren't possible with Managed Images. It's not documented, but you will receive an error upon image creation or VM deployment from image. The known work around for this is to replicate a snapshot rather than an image, build and attach the disk.

I'm wondering if we could add a --export-as-snapshot switch which would essentially general a snapshot of the VM in each image. The code is nearly identical (so I'd rather not create a second extension), and the only change would be .\create_target.py lines 126 - 134 which currently does an image create, rather than a snapshot create.


I scraped the CLI commands from the python and created a simple bash script for the time being, but the check that the python extension does are really clean and I'd much rather leverage what's already there.

Activity

  1. tamirkamara commented on Mar 7, 2019

    @tamirkamara
    Contributor

    Bennett Battistoni (@bebattis) the extension actually creates a snapshot just prior to the final image (lines you mentioned).
    I don't really understand what are those special images you are referring to. but at any case, if a managed image can't be created, what would be the source of the copy?

  2. bebattis commented on Mar 22, 2019

    @bebattis
    ContributorAuthor

    Tamir Kamara (@tamirkamara) I've submitted a PR. #583
    Hoping you can take a look and provide feedback.

  3. tamirkamara commented on Apr 4, 2019

    @tamirkamara
    Contributor

    Willie Xu (@williexu) the PR is merged so this issue can be closed.

  4. deancsmith commented on Apr 30, 2019

    @deancsmith

    Is there going to be a new release of the image-copy extension soon? There's been several PRs merged recently that we would love to use, but we can currently only use the official tagged releases.

    Apologies if there is a better place to ask this, and I couldn't find any details on the release cadence of these extensions published anywhere.

  5. tamirkamara commented on May 3, 2019

    @tamirkamara
    Contributor

    Yes - #669
    Sorry about the delay.

  6. added a commit that references this issue on Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions