-
Notifications
You must be signed in to change notification settings - Fork 79
refactor: Rename metrics-port to management-port #1012
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
refactor: Rename metrics-port to management-port #1012
Conversation
✅ Deploy Preview for polite-licorice-3db33c canceled.
|
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1012 +/- ##
=======================================
Coverage 71.96% 71.96%
=======================================
Files 28 28
Lines 2864 2864
=======================================
Hits 2061 2061
Misses 699 699
Partials 104 104 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Craig Pastro <craig.pastro@gmail.com>
Signed-off-by: Craig Pastro <craig.pastro@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes looks good. Like @beeme1mr said, we need to upadte Openfeature Operator to adapt to this configuration change. However, this change won't break exisiting configurations as we have fallback option for deprecated configuration option.
If we release flagd, @odubajDT is this something that we could include with beta version changeset ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this actually breaking with the change here? Doesn't this make it transparent?
Also we can perhaps log a warning if the deprecated option is used: https://github.com/open-feature/flagd/pull/1012/files#r1394782335
Signed-off-by: Craig Pastro <craig.pastro@gmail.com>
…craigpastro/flagd into metrics-port-to-management-port
Yeah this is not a breaking change. We can modify the PR title if we all agree :) |
@craigpastro is there actually a breaking change here? |
No, I wouldn’t call it such since it is still backwards compatible. There is the possibility that someone may use both |
🤖 I have created a release *beep* *boop* --- <details><summary>flagd: 0.7.1</summary> ## [0.7.1](flagd/v0.7.0...flagd/v0.7.1) (2023-11-28) ### 🐛 Bug Fixes * **deps:** update module github.com/open-feature/flagd/core to v0.7.0 ([#1014](#1014)) ([deec49e](deec49e)) ### 🔄 Refactoring * Rename metrics-port to management-port ([#1012](#1012)) ([5635e38](5635e38)) </details> <details><summary>flagd-proxy: 0.3.1</summary> ## [0.3.1](flagd-proxy/v0.3.0...flagd-proxy/v0.3.1) (2023-11-28) ### 🐛 Bug Fixes * **deps:** update module github.com/open-feature/flagd/core to v0.7.0 ([#1014](#1014)) ([deec49e](deec49e)) ### 🔄 Refactoring * Rename metrics-port to management-port ([#1012](#1012)) ([5635e38](5635e38)) </details> <details><summary>core: 0.7.1</summary> ## [0.7.1](core/v0.7.0...core/v0.7.1) (2023-11-28) ### 🐛 Bug Fixes * **deps:** update kubernetes packages to v0.28.4 ([#1016](#1016)) ([ae470e3](ae470e3)) * **deps:** update opentelemetry-go monorepo ([#1019](#1019)) ([23ae555](23ae555)) ### 🔄 Refactoring * Rename metrics-port to management-port ([#1012](#1012)) ([5635e38](5635e38)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This PR
--metrics-port
to--management-port
-m
now relates to--management-port
--metrics-port
--management-port
is set use that value (and possibly ignore--metrics-port
). If not and--metrics-port
is set use that value. Otherwise, use the default value.Related Issues
Resolves #867.
Notes
Follow-up Tasks
How to test