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

openshiftSCC property mismatch between front and api #845

Closed
titigmr opened this issue Aug 20, 2024 · 1 comment
Closed

openshiftSCC property mismatch between front and api #845

titigmr opened this issue Aug 20, 2024 · 1 comment

Comments

@titigmr
Copy link

titigmr commented Aug 20, 2024

The openshiftSCC injection is configured under services in api, however in the front is in global region

When we define the config openshift in region, the injection not work.

The current code is:

                },
                        "openshiftSCC":
                            apiRegion.openshiftSCC === undefined
                                ? undefined
                                : {
                                      "scc": apiRegion.openshiftSCC.scc,
                                      "enabled": apiRegion.openshiftSCC.enabled
                                  }
                    })

I think this changes fix the issue:

                },
                        "openshiftSCC":
                            apiRegion.services.openshiftSCC === undefined
                                ? undefined
                                : {
                                      "scc": apiRegion.services.openshiftSCC.scc,
                                      "enabled": apiRegion.services.openshiftSCC.enabled
                                  }
                    })
garronej added a commit that referenced this issue Aug 20, 2024
@garronej
Copy link
Contributor

Hello @titigmr,

Sorry for the mistake and thanks you for reporting the issue.

I've just released a new version with the fix. It should be available to use in about 15 minutes.

Best

garronej added a commit that referenced this issue Aug 20, 2024
garronej added a commit that referenced this issue Aug 20, 2024
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

No branches or pull requests

2 participants