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

Installer - allow to override default kyma configuration when using installation/cmd/run.sh #3995

Closed
aszecowka opened this issue May 9, 2019 · 5 comments
Labels
area/installation Issues or PRs related to installation kind/feature Categorizes issue or PR as related to a new feature.

Comments

@aszecowka
Copy link
Contributor

When I want to modify default kyma configuration I have to create configmap with label installer=overrides.
But when I start kyma on minikube by executing installation/cmd/run.sh script it is not so easy to do this.
There a configure-components.sh script that allows me to do that, but:

  • it is not documented
  • it removes my custom configuration after applying it. Instead, this file for defining overrides should be added to the gitignore file.

Currently, overrides can be defined in components.env file, consider renaming it.

@aszecowka aszecowka added kind/feature Categorizes issue or PR as related to a new feature. area/installation Issues or PRs related to installation labels May 9, 2019
@Disper
Copy link
Member

Disper commented May 15, 2019

@aszecowka please adjust the issue to the template

@derberg
Copy link

derberg commented May 17, 2019

@a-thaler how does it look like with Kyma CLI? I would say this issue should not really be taken into account as CLI will remove those scripts, so maybe just let's have it as feature request for Kyma CLI?

@lszymik lszymik added this to the Backlog_Goat milestone May 22, 2019
@a-thaler
Copy link
Contributor

I think it is a good idea to not invest here anymore but instead have a good solution provided by CLI, I created an epic for that: kyma-project/cli#89

@stale
Copy link

stale bot commented Jul 21, 2019

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 21, 2019
@tomekpapiernik
Copy link
Contributor

tomekpapiernik commented Jul 24, 2019

Script deprecated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/installation Issues or PRs related to installation kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

6 participants