-
Notifications
You must be signed in to change notification settings - Fork 351
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
chore(knative): configure via properties #5186
Conversation
Part of #5090 - @lburgazzoli please, have a look and confirm if this part is good. |
22c60e8
to
69f0591
Compare
✔️ Unit test coverage report - coverage increased from 36% to 36.2% (+0.2%) |
69f0591
to
8807e50
Compare
If tests are green and @lburgazzoli is fine with the development, we can merge this. |
✔️ Unit test coverage report - coverage increased from 36% to 36.2% (+0.2%) |
Known flaky check failure. Merging. |
do we have an issue to track the flaky test ? |
Probably not. This is happening because some sync problem in github actions OS when running the --dev and watching files. We've planned to deprecate the |
it is more for knowledge sharing so everyone knows why we merged something with failing tests and we can check the issue to be solved when moving to the new architecture |
With this PR we move the configuration from the env var to the properties.
Release Note