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 1) #7

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

User Story: Proxy Config Download (Version 1) #7

Bhoomiz01 opened this issue Dec 26, 2024 · 0 comments

Comments

@Bhoomiz01
Copy link
Collaborator

Title:

As a user, I want to download a separate config for each cluster so that I can access them individually.


Description:

In this version, users can download a configuration file for every cluster they need to access. The configuration file will be available for download via the local Gangway interface.


Acceptance Criteria:

  1. Config Availability:

    • A separate configuration file is generated for each cluster.
    • The config file includes all necessary details for the user to access the respective cluster.
  2. Gangway Integration:

    • Users can log in to the local Gangway interface.
    • A "Download Config" button is available for the cluster.
  3. Config Download Functionality:

    • Upon clicking "Download Config," the corresponding cluster’s config file is downloaded.
    • The downloaded file is correctly formatted and functional for cluster access.
  4. Validation:

    • Users can successfully use the downloaded config file to access the intended cluster.

Preconditions:

  1. Gangway is deployed and operational for the environment.
  2. User credentials and roles are set up, allowing access to specific clusters.
  3. The backend generates valid config files for each cluster.

Steps for Validation:

  1. Login to Gangway:

    • User logs in to the local Gangway interface using their credentials.
  2. Download Config:

    • For each cluster, the user clicks the "Download Config" button.
    • Validate that a correctly named file (e.g., <cluster_name>-config.yaml) is downloaded.
  3. Test Config Functionality:

    • Use the downloaded config file to connect to the corresponding cluster via kubectl.
    • Verify that cluster access is established and operational.
  4. Error Handling:

    • Test scenarios where the user attempts to download a config without access permissions.
    • Confirm that appropriate error messages are displayed, and no invalid config file is generated.
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