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

User Story: Proxy Config Download (Version 3) #12

Open
Bhoomiz01 opened this issue Dec 27, 2024 · 0 comments
Open

User Story: Proxy Config Download (Version 3) #12

Bhoomiz01 opened this issue Dec 27, 2024 · 0 comments

Comments

@Bhoomiz01
Copy link
Collaborator

Title:

As a user, I want to download a single config containing an array of clusters directly from the Ops-dashboard so that I can access all the clusters I have been granted access to.


Description:

In this version, users can log in to the Ops-dashboard and navigate to a dedicated "Clusters" page. On this page, they will see a "Download Config" button, which allows them to download a unified configuration file containing details for all clusters they have access to.


Acceptance Criteria:

  1. Clusters Page:

    • A "Clusters" page is available on the Ops-dashboard.
  2. Download Config Button:

    • A "Download Config" button is displayed on the "Clusters" page.
    • Clicking the button generates and downloads a single unified config file.
  3. Unified Config File:

    • The downloaded config file contains an array of all clusters the user has access to.
  4. Access Control:

    • The config dynamically updates based on the clusters the admin has granted or revoked access to.
  5. Validation:

    • Users can successfully download the config and use it to access all authorized clusters.

Preconditions:

  1. Ops-dashboard is deployed and operational.
  2. User credentials and roles are set up, determining cluster access.

Steps for Validation:

  1. Login to Ops-dashboard:

    • User logs in to the Ops-dashboard using their credentials.
  2. Navigate to Clusters Page:

    • User navigates to the "Clusters" page.
    • Validate that the page displays clusters the user has access to.
  3. Download Config:

    • User clicks the "Download Config" button.
    • Validate that the downloaded file contains details for all authorized clusters.
  4. Test Config Functionality:

    • Use the unified config file with kubectl to verify access to all clusters listed in the file.
  5. Access Updates:

    • Grant or revoke access to clusters for the user.
    • Verify that the updated config file reflects these changes after download.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant