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

Manage restricted attributes for images and vnets on Sunstone #6332

Closed
3 tasks done
dcarracedo opened this issue Sep 26, 2023 · 0 comments · Fixed by OpenNebula/docs#2770 or OpenNebula/docs#2771
Closed
3 tasks done

Comments

@dcarracedo
Copy link
Contributor

dcarracedo commented Sep 26, 2023

Description
In one config we have some attributes set as restricted, so a regular user cannot create, update or delete these attributes. In #6154 the restricted attributes of a virtual machine are managed in Fireedge Sunstone to avoid that an user can create, update or delete.

On this feature, we need to do the same but with the attributes for images and virtual networks.

Use case
The non admin users will use this feature to avoid errors and manage images and virtual networks without any problem.

Interface Changes
On Fireedge Sunstone, int the forms to create/update images and virtual networks, the restricted attributes will be show as read only because the user can see it but not modify it.
Also, a non admin user cannot delete an image or a virtual network if one of them has restricted attributes.

Additional Context
Use the disable disableFields function to manage this fields.

Progress Status

  • Code committed
  • Testing - QA
  • Documentation (Release notes - resolved issues, compatibility, known issues)
@tinova tinova added this to the Release 6.8.1 milestone Sep 26, 2023
dcarracedo added a commit to OpenNebula/docs that referenced this issue Nov 23, 2023
Signed-off-by: David Carracedo <dcarracedo@opennebula.io>
dcarracedo added a commit to OpenNebula/docs that referenced this issue Nov 23, 2023
Signed-off-by: David Carracedo <dcarracedo@opennebula.io>
dcarracedo added a commit to OpenNebula/docs that referenced this issue Nov 23, 2023
dcarracedo added a commit to OpenNebula/docs that referenced this issue Nov 23, 2023
Signed-off-by: David Carracedo <dcarracedo@opennebula.io>
@tinova tinova closed this as completed Nov 23, 2023
tinova pushed a commit to OpenNebula/docs that referenced this issue Nov 23, 2023
tinova pushed a commit to OpenNebula/docs that referenced this issue Nov 23, 2023
rsmontero pushed a commit that referenced this issue Nov 23, 2023
Co-authored-by: Tino Vázquez <cvazquez@opennebula.io>
@tinova tinova reopened this Nov 29, 2023
@tinova tinova closed this as completed Dec 1, 2023
rsmontero pushed a commit that referenced this issue Mar 11, 2024
Co-authored-by: Tino Vázquez <cvazquez@opennebula.io>
(cherry picked from commit c9ed2fe)
rsmontero pushed a commit that referenced this issue Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment