Skip to content

Conversation

@rooftopcellist
Copy link
Member

@rooftopcellist rooftopcellist commented Jul 2, 2025

Summary

This PR adds the ability to configure which EDA Custom Resource (CR) file to apply during deployment via the EDA_CR environment variable, replacing the previous approach of manually un-commenting different CR files in the script.

Changes

  • Added EDA_CR environment variable with default value dev/eda-cr/eda-openshift-cr.yml
  • Simplified CR application logic by removing hardcoded file path and commented alternatives
  • Enhanced user experience with:
    • Clear feedback showing which CR file is being applied
    • List of available CR files displayed before deployment
    • Updated usage documentation with examples

Usage Examples

Default behavior (unchanged):

NAMESPACE=eda ./up.sh

Using a custom CR file:

NAMESPACE=eda TAG=dev EDA_CR=dev/eda-cr/lightweight-eda.yml ./up.sh

- Add EDA_CR env var to up.sh to specify custom CR file
  - Defaults to dev/eda-cr/eda-openshift-cr.yml
  - Replace hardcoded CR selection with configurable approach
  - Add feedback showing which CR file is being applied
  - Display available CR files for user reference
- Update usage examples in both scripts
@rooftopcellist rooftopcellist force-pushed the configurable-eda-cr-up-script branch from 07a07e0 to 5657a56 Compare July 8, 2025 22:51
@sonarqubecloud
Copy link

sonarqubecloud bot commented Jul 8, 2025

Copy link
Contributor

@Alex-Izquierdo Alex-Izquierdo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This already contains the commit from #292
Except for that, LGTM

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants