-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Expose current branch
and version
to config deprecation providers
#113600
Expose current branch
and version
to config deprecation providers
#113600
Conversation
branch
and version
to deprecation providersbranch
and version
to config deprecation providers
retest |
Pinging @elastic/kibana-core (Team:Core) |
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.
Alerting changes LGTM
Pinging @elastic/fleet (Team:Fleet) |
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.
Fleet changes LGTM
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 in Security/Spaces deprecation tests LGTM.
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.
AppServices test mock changes LGTM
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.
Adding the context here is going to make life so much easier down the road if and when we need to hunt down when something was deprecated. Nice work!
LGTM 😄
@@ -229,4 +248,5 @@ export interface ConfigDeprecationFactory { | |||
export interface ConfigDeprecationWithContext { | |||
deprecation: ConfigDeprecation; | |||
path: string; | |||
context: ConfigDeprecationContext; |
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.
The context
is going to make our lives so much easier down the road!
|
||
const createDeprecationContext = (env: Env): ConfigDeprecationContext => { | ||
return { | ||
branch: env.packageInfo.branch, |
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.
I was looking at the type changes and started thinking about validation immediately. Now it all makes sense! 😄
💚 Build SucceededMetrics [docs]Public APIs missing comments
History
To update your PR or re-run it, just comment with: |
…elastic#113600) * Expose deprecation context to config deprecations * fix import * add correct doc annotations * fix another test file * update generated doc * fix yet another test file * fix more types * add proper mock * fix import
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
…elastic#113600) * Expose deprecation context to config deprecations * fix import * add correct doc annotations * fix another test file * update generated doc * fix yet another test file * fix more types * add proper mock * fix import
…viders (#113600) (#114067) * Expose current `branch` and `version` to config deprecation providers (#113600) * Expose deprecation context to config deprecations * fix import * add correct doc annotations * fix another test file * update generated doc * fix yet another test file * fix more types * add proper mock * fix import * lint ? * restore changes to files removed in master
This was made possible via PR elastic#113600.
This was made possible via PR elastic#113600.
@pgayvallet on APM I use core.deprecations.registerDeprecations to register a deprecation. I do it because I need to fetch some information on |
@cauemarcondes We have a separate issue to track adding the branch info in In the meantime, if you are using |
Summary
Fix #112221
Introduce a new
ConfigDeprecationContext
type containing the currentbranch
andversion
, and expose it as an additional parameter toConfigDeprecation
.Example
Checklist