Skip to content
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

Set new templates with specified vm-init #760

Merged
merged 1 commit into from
Dec 5, 2022

Commits on Nov 27, 2022

  1. core, webadmin: set new templates with specified vm-init

    Previously, the backend (AddVmTemplate) set new templates with the vm-init
    configuration of the VM that they were created from. This prevented users
    from creating templates with modified vm-init configuration or without vm-
    init configuration from VMs that are set with vm-init. Users could either
    change the VM first or modify the created template to achieve this.
    
    Now, the backend respects the vm-init configuration that is specified by
    clients. While the handling of vm-init in REST-API works well, the UI
    did not pass the vm-init configuration of the VM that templates were
    created from. Therefore, the webadmin is changed to load the vm-init
    configuration of the VM that a template is created from and pass it to
    the backend now.
    
    Signed-off-by: Arik Hadas <ahadas@redhat.com>
    ahadas committed Nov 27, 2022
    Configuration menu
    Copy the full SHA
    4448449 View commit details
    Browse the repository at this point in the history