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: Adding a New Cluster to the Config (Version 2) #10

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

User Story: Adding a New Cluster to the Config (Version 2) #10

Bhoomiz01 opened this issue Dec 27, 2024 · 2 comments

Comments

@Bhoomiz01
Copy link
Collaborator

Title:
As a user, I want the unified config file to include new clusters I gain access to so that I can access them without requiring multiple configs.


Description:

When a user gains access to a new cluster, the unified configuration file is updated to include the new cluster's details. Users must download the updated config from the Gangway interface.


Acceptance Criteria:

  1. Config Update:

    • When new cluster access is granted, the unified config file reflects the updated list of clusters.
  2. Gangway Integration:

    • The "Download Unified Config" button provides the updated file after new cluster access is granted.
  3. Validation:

    • Users can download the updated config file and use it to access the newly added cluster.

Steps for Validation:

  1. Grant the user access to a new cluster.
  2. Ensure the updated config file includes the new cluster.
  3. Use the config file to verify access to all clusters, including the newly added one.

@Bhoomiz01 Bhoomiz01 changed the title User Story 2: Adding a New Cluster to the Config (Version 2) User Story: Adding a New Cluster to the Config (Version 2) Dec 27, 2024
@munir131
Copy link
Member

Consider Gangway as quick solution for value delivery in initial sprints. Proper solution is download from Ops dashboard using keycloak authz

@Bhoomiz01
Copy link
Collaborator Author

Consider Gangway as quick solution for value delivery in initial sprints. Proper solution is download from Ops dashboard using keycloak authz

Yes, I am making a version 3 user story for this.

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

2 participants