Description
Summary
We are introducing a new licensing tier - "Premium" - and should update our licensing badges in the UI so that they appropriately communicate a feature's licensing level to the user.
Background
We indicate licensing for specific features with pills, e.g. in the screenshot below, appearance configuration is an enterprise feature which is currently accessible to the user:
Alongside the enterprise pill we see an entitled pill which indicates whether or not a user has a valid license to use that feature as some (but not all) features may be administratively enabled or disabled at the deployment level. If a feature is both entitled and enabled, then it is used on the deployment.
After we GA orgs, we don't want to expose Enterprise as an available plan to OSS users as Premium will be our only paid tier going forward; however, we do need to retain an enterprise badge for existing Enterprise customers so that they may differentiate between features they have access to and features they don't (Premium features).
Requirements
- First, let's remove all
entitledbadges from our UI. While the concept of entitlement are still valid within our product, we will find another way at another time to convey that meaning to users - Create a badge component that accepts licensing info and toggle the label in that badge based on the below table:
| enterprise feature | premium feature
premium license | 'premium' | 'premium'
enterpr license | 'enterprise' | 'premium'
no license | 'premium' | 'premium'
- Ensure the Premium badge state displays the appropriate licensing info tooltip (and documentation link!) on hover, e.g.
- Ensure there is no tooltip or documentation link on
Enterprisebadges as this concept will no longer exist in our documentation