René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Improve Useability of ACL Rules for Large Scale Projects (or long term maintanence)","articleBody":"\u003c!--\r\nVerify first that your issue/request is not already reported on GitHub.\r\nAlso test if the latest release and main branch are affected too.\r\nAlways add information AFTER of these HTML comments, but no need to delete the comments.\r\n--\u003e\r\n\r\n##### ISSUE TYPE\r\n\u003c!-- Pick one below and delete the rest --\u003e\r\n * Improvement Request\r\n \r\n##### COMPONENT NAME\r\n\u003c!--\r\nCategorize the issue, e.g. API, VR, VPN, UI, etc.\r\n--\u003e\r\n~~~\r\nImprovement Request (UI, Functionality)\r\n~~~\r\n\r\n##### CLOUDSTACK VERSION\r\n\u003c!--\r\nNew line separated list of affected versions, commit ID for issues on main branch.\r\n--\u003e\r\n\r\n~~~\r\n4.19\r\n~~~\r\n\r\n##### CONFIGURATION\r\n\u003c!--\r\nInformation about the configuration if relevant, e.g. basic network, advanced networking, etc.  N/A otherwise\r\n--\u003e\r\nN/A\r\n\r\n##### OS / ENVIRONMENT\r\n\u003c!--\r\nInformation about the environment if relevant, N/A otherwise\r\n--\u003e\r\nN/A\r\n\r\n##### SUMMARY\r\n\u003c!-- Explain the problem/feature briefly --\u003e\r\n\r\nAs an admin, I find creating and manaing ACL Rules to be painful at the moment. \r\n\r\nHere are a few ideas id like to propose to improve the useability for long term, and large scale projects.\r\n\r\n**1. Display ACL Rules in the form of a excel like table** \r\n- Currently the UI for ACL Rules is in a 2x4 Column\r\n- It makes it hard to scan and read. \r\n- Also, depending on the input, the columns can be hidden/shown. Which makes it even harder to read as every rule can have a different arrangement. \r\n\r\n**2. Allow users to import ACL from a CSV File**\r\n- As an admin, id like the ability to plan my ACL lists offline first in an excel.\r\n- Once ive finalised my list, i would like to be able to import it to cloudstack via CSV\r\n- This would greatly help my workflow (i can also keep the excel as a backup)\r\n\r\n**3. Allow users to Search ACL Rule**\r\n- In large scale projects like ours, we have around 20-40 ACL Rules.\r\n- As the rules increase, its hard to read and identify. \r\n- Supporting search ACL Rule would help. \r\n\r\n**4. Display Tags in the UI for each ACL Rule**\r\n- Tags are supported in the GUI, but they are not displayed. \r\n- If tags are shown in the UI, it makes it easier to scan\r\n\r\n**5. Support ability to Filter by Tags**\r\n- This is self explanatory, makes managing ACL rules easier for large lists. \r\n\r\n**6. Allow user to create an ACL Rule for Multiple Ports**\r\n- I remember reading somewhere that the logic is supported (Eg. Terraform Provider Docs)\r\n- But the UI doesnt seem to support it. \r\n- This will help greatly reduce the number of rules we create. \r\n\r\n**7. Export ACL List is missing some data**\r\n- For example, 'Ports' are not available in the exported CSV when exported. \r\n- There may be others that are missing from the CSV output too. \r\n\r\n**8. Support ACL on Public IP**\r\n- Good to have, adds more security\r\n\r\n**9. Support Destination CIDR**\r\n- Good to have, adds more security\r\n- Reduces number of ACL Rules required\r\n\r\n**10. Option to set ACL Rule to be the very bottom by default**\r\n- At the very end of our ACL Rule, we usually have a 'Deny All'\r\n- But when i use API or Terraform to create ACL Rules, the arrangement and sequence (including the rule number) gets all messed up. \r\n- Would be great if we could have a parameter and function in the UI to make the rule fix itself at the bottom of the list.\r\n\r\nI know its a long list. Thank you for reading!\r\n\r\n##### STEPS TO REPRODUCE\r\n\u003c!--\r\nFor bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.\r\n\r\nFor new features, show how the feature would be used.\r\n--\u003e\r\n\r\n\u003c!-- Paste example playbooks or commands between quotes below --\u003e\r\n~~~\r\nExperiencing this issue cause our projects are getting bigger and bigger.\r\n~~~\r\n\r\n\u003c!-- You can also paste gist.github.com links for larger files --\u003e\r\n\r\n##### EXPECTED RESULTS\r\n\u003c!-- What did you expect to happen when running the steps above? --\u003e\r\n\r\n~~~\r\nBetter experience using ACL Rules\r\n~~~\r\n\r\n##### ACTUAL RESULTS\r\n\u003c!-- What actually happened? --\u003e\r\n\r\n\u003c!-- Paste verbatim command output between quotes below --\u003e\r\n~~~\r\nChallenging to use ACL rules for large scale projects.\r\n~~~\r\n","author":{"url":"https://github.com/btzq","@type":"Person","name":"btzq"},"datePublished":"2024-03-27T14:59:07.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/8841/cloudstack/issues/8841"}