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

[APM] Use licensing from context #70118

Merged
merged 3 commits into from
Jun 29, 2020
Merged

Conversation

smith
Copy link
Contributor

@smith smith commented Jun 26, 2020

We added the usage of featureUsage.notifyUsage from the licensing plugin in #69455.

This required us to use getStartServices to add licensingtocontext.plugins`.

In #69838 featureUsage was added to context.licensing, so we don't need to add it to context.plugins.

We added the usage of `featureUsage.notifyUsage` from the licensing plugin in elastic#69455.

This required us to use `getStartServices to add `licensing` to `context.plugins`.

In elastic#69838 `featureUsage` was added to `context.licensing`, so we don't need to add it to `context.plugins`.
@smith smith requested a review from a team as a code owner June 26, 2020 19:59
@botelastic botelastic bot added the Team:APM All issues that need APM UI Team support label Jun 26, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui (Team:apm)

@smith smith added release_note:skip Skip the PR/issue when compiling release notes v7.9.0 labels Jun 26, 2020
@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Build metrics

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@smith smith merged commit 8e57db6 into elastic:master Jun 29, 2020
@smith smith deleted the nls/licensing-update branch June 29, 2020 13:23
smith added a commit to smith/kibana that referenced this pull request Jun 29, 2020
* [APM] Use licensing from context

We added the usage of `featureUsage.notifyUsage` from the licensing plugin in elastic#69455.

This required us to use `getStartServices to add `licensing` to `context.plugins`.

In elastic#69838 `featureUsage` was added to `context.licensing`, so we don't need to add it to `context.plugins`.
smith added a commit that referenced this pull request Jun 29, 2020
* [APM] Use licensing from context

We added the usage of `featureUsage.notifyUsage` from the licensing plugin in #69455.

This required us to use `getStartServices to add `licensing` to `context.plugins`.

In #69838 `featureUsage` was added to `context.licensing`, so we don't need to add it to `context.plugins`.
Bamieh pushed a commit to Bamieh/kibana that referenced this pull request Jul 1, 2020
* [APM] Use licensing from context

We added the usage of `featureUsage.notifyUsage` from the licensing plugin in elastic#69455.

This required us to use `getStartServices to add `licensing` to `context.plugins`.

In elastic#69838 `featureUsage` was added to `context.licensing`, so we don't need to add it to `context.plugins`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:skip Skip the PR/issue when compiling release notes Team:APM All issues that need APM UI Team support v7.9.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants