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

Remove experimental code app #49404

Merged
merged 13 commits into from
Oct 28, 2019
Merged

Remove experimental code app #49404

merged 13 commits into from
Oct 28, 2019

Conversation

epixa
Copy link
Contributor

@epixa epixa commented Oct 25, 2019

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:

  1. The 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
  2. The code plugin documentation is removed entirely. A separate PR will add a deprecation notice to docs for already-shipped versions.
  3. Despite still existing on the file system, the legacy code is no longer imported into the xpack module and thus is not executed when Kibana starts up.
  4. All code plugin functional tests are removed.
  5. The legacy plugin is deleted, and the NP plugin shell is replaced with config deprecation. You can scroll down to see this particular part of the change or go directly to the remaining plugin files: plugin.ts and plugin.test.ts
  6. Remove xpack.code translations

@elasticmachine
Copy link
Contributor

Pinging @elastic/code (Team:Code)

@tylersmalley
Copy link
Contributor

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?

@epixa
Copy link
Contributor Author

epixa commented Oct 25, 2019

@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.

@epixa
Copy link
Contributor Author

epixa commented Oct 25, 2019

Actually, the implementations of px appear to be identical, so I think this is fine:

apm: https://github.com/elastic/kibana/blob/master/x-pack/legacy/plugins/apm/public/style/variables.ts#L22-L24
code: https://github.com/elastic/kibana/blob/master/x-pack/legacy/plugins/code/public/style/variables.ts#L9-L11

@elasticmachine

This comment has been minimized.

@elasticmachine

This comment has been minimized.

@epixa
Copy link
Contributor Author

epixa commented Oct 26, 2019

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.

@elasticmachine

This comment has been minimized.

@elasticmachine

This comment has been minimized.

@elasticmachine

This comment has been minimized.

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@epixa epixa added the review label Oct 26, 2019
@epixa epixa requested review from a team as code owners October 26, 2019 11:27
Copy link
Contributor

@spalger spalger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@snide snide left a 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.

This was referenced Oct 27, 2019
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@epixa epixa merged commit 0b82cfe into elastic:master Oct 28, 2019
@epixa epixa deleted the remove-code branch October 28, 2019 15:40
epixa added a commit that referenced this pull request Oct 28, 2019
* 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
Copy link
Contributor Author

epixa commented Oct 28, 2019

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

epixa added a commit that referenced this pull request Oct 28, 2019
* 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
@narcher7
Copy link
Contributor

narcher7 commented Nov 7, 2019

@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?

@epixa
Copy link
Contributor Author

epixa commented Nov 11, 2019

@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.

@narcher7
Copy link
Contributor

@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?

@tylersmalley
Copy link
Contributor

@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.

@narcher7
Copy link
Contributor

@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?

@epixa
Copy link
Contributor Author

epixa commented Nov 18, 2019

Yes, I should have included that in the original PR. I'll submit breaking change docs for this today or first thing tomorrow.

@willemdh
Copy link

Sad to see this feature go. We really liked to Kibana Code application to search in all our git repo's.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants