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

Streamline Environment Configuration and Service Selection #813

Open
luigimolinaro opened this issue Oct 18, 2024 · 0 comments
Open

Streamline Environment Configuration and Service Selection #813

luigimolinaro opened this issue Oct 18, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@luigimolinaro
Copy link
Contributor

The current process for setting up and configuring IBM Cloud Pak Deployer requires manual input for environment variables, directory paths, and installed services, which can be complex and prone to mistakes, particularly for users who are not familiar with the system. Non-expert users may find it challenging to set up their environment correctly without guidance.

Describe the solution you'd like

  1. Automating the configuration of environment variables:
    • The system would prompt users for key information such as the entitlement key, directory paths, and OpenShift login credentials, and automatically generate a config.yaml file.
    • Provide users with the option to update existing config.yaml files through an interactive interface that allows them to modify environment variables without manual edits.
  2. Service Selection:
    • The system should allow users to select which services to install during deployment (e.g., selecting specific Cloud Pak modules or cartridges).
    • This can be presented as a menu of options where users can check the services they want to install, helping them tailor the deployment to their specific needs.
    • This functionality would also validate the selections, ensuring compatibility and completeness before proceeding with installation.
  3. Ensures a standardized directory structure where key files (e.g., environment setup scripts) are placed at the same directory level as the configuration and status directories. This will simplify ongoing maintenance, such as adding cartridges or performing upgrades.
@luigimolinaro luigimolinaro self-assigned this Oct 18, 2024
@luigimolinaro luigimolinaro added the enhancement New feature or request label Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant