add a mz_license_keys catalog table #33121
Conversation
doy-materialize
force-pushed
the
push-urnrryqkvwwt
branch
from
fc448f6 to
f06fa09
Compare
| if !catalog.state.license_key.id.is_empty() { | ||
| builtin_table_updates.push( | ||
| catalog.state.resolve_builtin_table_update( | ||
| catalog | ||
| .state | ||
| .pack_license_key_update(&catalog.state.license_key)?, | ||
| ), | ||
| ); | ||
| } | ||
|
|
There was a problem hiding this comment.
hmmm.. does this get cleared on restart? Just trying to think the the license key update story.
There was a problem hiding this comment.
i'll verify this tomorrow, but i'm pretty confident that this gets reset on every restart (it's the same codepath that the egress ip table uses)
There was a problem hiding this comment.
yeah, this updates on restart.
doy-materialize
force-pushed
the
push-urnrryqkvwwt
branch
3 times, most recently
from
f7e1288 to
d44d55b
Compare
| | Field | Type | Meaning | | ||
| | ----------- | ----------- | -------- | | ||
| | `id` | [`text`] | The identifier of this particular license key. | | ||
| | `organization` | [`text`] | The name of the organization that this license key was issued to. | |
There was a problem hiding this comment.
Just for my edification ... does this organization map to something like the company name associated with the account setting?
There was a problem hiding this comment.
yeah, it's just an arbitrary string identifying the organization that this license key was issued to. for now, it's just the frontegg tenant id for the customer, but it could be anything (i think for community edition license keys, it will probably be the user's email address, for instance)
| | ----------- | ----------- | -------- | | ||
| | `id` | [`text`] | The identifier of this particular license key. | | ||
| | `organization` | [`text`] | The name of the organization that this license key was issued to. | | ||
| | `environment_id` | [`text`] | The environment ID that this license key was issued for. | |
There was a problem hiding this comment.
Also, just for my edification ... what does the environment_id map to? (heh heh ... I'm sure it's in some design doc somewhere)
There was a problem hiding this comment.
environment_id is the use case id which corresponds to the --environment-id flag passed to environmentd
doy-materialize
force-pushed
the
push-urnrryqkvwwt
branch
3 times, most recently
from
8e8e65f to
8e653f4
Compare
since we want to be able to display them to the user
doy-materialize
force-pushed
the
push-urnrryqkvwwt
branch
from
8e653f4 to
07ba26c
Compare
Motivation
we'll want to be able to have a page in the self-managed console which displays license key metadata so that users can see when their key is going to expire
Checklist
$T ⇔ Proto$Tmapping (possibly in a backwards-incompatible way), then it is tagged with aT-protolabel.