-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Remove experimental code app #49404
Remove experimental code app #49404
Conversation
Pinging @elastic/code (Team:Code) |
Just to confirm since the variables files appear to be different. Do we want to copy the code one over to APM since that is what they were using? |
@tylersmalley that's a question for @sqren really. He told me to just use the one from the apm plugin, and I don't really know the implications. |
Actually, the implementations of apm: https://github.com/elastic/kibana/blob/master/x-pack/legacy/plugins/apm/public/style/variables.ts#L22-L24 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I'm pretty sure the previous CI failure was a jenkins issue during shutdown after the CI jobs were green, but just in case I merged master to kick off another build. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
💚 Build Succeeded |
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.
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.
Checked to make sure the scss stuff is local to code. OKed from design.
💚 Build Succeeded |
* Fix erroneous code plugin import in apm * Stop running legacy code plugin * Stop testing code app and apis * Remove code plugin source and deprecate config * Remove code plugin docs * Remove xpack.code translations * Remove code import on api_integration * Remove code privilege from security test * remove two more mentions of code * remove code es_archives * remove code doc images
FYI: Due to the exceptional nature of this change, we agreed to do it in 7.5.0 as well despite it being after FF. If push came to shove, we can delay that release. /cc @clintongormley |
* Fix erroneous code plugin import in apm * Stop running legacy code plugin * Stop testing code app and apis * Remove code plugin source and deprecate config * Remove code plugin docs * Remove xpack.code translations * Remove code import on api_integration * Remove code privilege from security test * remove two more mentions of code * remove code es_archives * remove code doc images
@epixa: Late to the game on this one, but do we plan on backporting this change all the way back to 7.2 when the Code app was introduced? |
@Donnater No. Those versions are no longer maintained, so they won't be getting new releases. We could technically still do this in 7.4 since that is still maintained, but we'd prefer not to do this in a patch release. The code plugin is disabled by default in those versions, so most people don't use it anyway. |
@epixa: The issue is that the Code docs are still listed in those older versions. I can try to make a pull request that just pulls out docs, but would it be possible to just cherry-pick the doc related commits from this PR and just push those down to 7.4 and 7.3? |
@Donnater, is there a reason we want to remove the docs for the versions it's in? For users who might be using Code in one of those versions, I think it's fair that they should still have access to those docs. |
@tylersmalley: Not a good reason besides consistency. General question to the group, is there a need to add this to the breaking changes list of 7.5? How many people were actually using the code app before we switched it off? |
Yes, I should have included that in the original PR. I'll submit breaking change docs for this today or first thing tomorrow. |
Sad to see this feature go. We really liked to Kibana Code application to search in all our git repo's. |
Summary
We've been experimenting with the code app for awhile now, but it just isn't fitting together the way we want it to, so we've decided not to pursue a code integration right now. To that end, we're removing the code plugin from future releases.
Since the code app was disabled by default, this shouldn't have an impact on most Kibana deployments. For those that explicitly enabled code, the app will no longer be available and a deprecation warning will be shown on startup due to lingering
xpack.code.*
configurations in kibana.yml. The plan will be (though it won't be implemented in this PR) that from 8.0 onward, any remainingxpack.code.*
configurations in kibana.yml will be treated as unknown configurations and will fail Kibana startup.Due to the amount of source code being removed, this pull request is too large to review in one go. Instead, it is best to review the individual commits, which break down like so:
apm
plugin was accidentally importing a function from the code plugin rather than the duplicate function that already existed in their own plugin, so that import statement is corrected under advisement from @sqren