[TIP] Restrict content visibility for non-enterprise users

[lgestc]

Summary

I think this unit test sums it up best.

In short, this will restrict the nested components visiblity and render the fallback instead if
the user is below enterprise tier.

Checklist

Delete any items that are not applicable to this PR.

• Unit or functional tests were updated or added to match the most common scenarios

[maxcold]

am I correct that we keep our page in the navigation, but render nothing when not on enterprise? This approach is great if in the future we want to render "upgrade your license" fallback, but I think if we go with no fallback, then we would like to hide the app completely as with the feature flag - basically no nav item, no page available via direct link (redirect to Security Overview or smth). While we are waiting for the decision on the "upgrade your license block" and have our feature flag I think we can go ahead and merge it, but can happen that we will need to update the logic once more

[lgestc]

am I correct that we keep our page in the navigation, but render nothing when not on enterprise? This approach is great if in the future we want to render "upgrade your license" fallback, but I think if we go with no fallback, then we would like to hide the app completely as with the feature flag - basically no nav item, no page available via direct link (redirect to Security Overview or smth). While we are waiting for the decision on the "upgrade your license block" and have our feature flag I think we can go ahead and merge it, but can happen that we will need to update the logic once more

According to the comment in parent issue (on mobile, cannot paste it) - we are not going to hide anything in the nav. :)

I will implement the specific fallback once the design is ready.

[PhilippeOberti]

@maxcold @lgmys looking at this comment from the Security Solution, it seems they don't care about having the plugin load but show nothing...

Changes are implemented. I used a Redirect to the base route (goes to Get Started) when the Threat Intelligence feature isn't enabled

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: d43d086

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
threatIntelligence	115	118	+3

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
threatIntelligence	5	6	+1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
securitySolution	5.6MB	5.6MB	+20.0B
threatIntelligence	62.5KB	62.3KB	-111.0B
total			-91.0B

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
threatIntelligence	0	1	+1

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
threatIntelligence	4.8KB	5.2KB	+410.0B

Unknown metric groups

API count

id	before	after	diff
threatIntelligence	5	6	+1

History

• 💔 Build #63141 failed 406c5d96e211fc4298dfe0a7cfb222b091b2eefe
• 💔 Build #63133 failed e5a1f5bad7270d9ff1d336490223514d566c54d2
• 💔 Build #63129 failed e5839507c67acd775cbbf44d2b63bfe196a8c878

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

[maxcold]

@lgmys makes sense, as we are going with the fallback component "upgrade your license" the approach in the PR is good!

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.4

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation