updated instructions in account token regeneration modal (#897)

This commit is contained in:
Michael Quigley 2025-02-26 13:15:29 -05:00
parent cf3f3c1fd6
commit b167e03648
No known key found for this signature in database
GPG Key ID: 9B60314A9DD20A62

View File

@ -84,18 +84,25 @@ const RegenerateAccountTokenModal = ({ close, isOpen, user }: RegenerateAccountT
</Grid2> </Grid2>
<Grid2 container sx={{ flexGrow: 1, p: 1 }} alignItems="center"> <Grid2 container sx={{ flexGrow: 1, p: 1 }} alignItems="center">
<Typography> <Typography>
You will need to manually edit your <code>$&#123;HOME&#125;/.zrok/environment.json</code> files You will need to use the <code> zrok rebase accountToken </code> command to update any enabled
(in each environment) to use the new <code>zrok_token</code>. Updating these files will restore environments to use your new account token. Rebasing your environments will minimize any service
the functionality of your environments. disruptions caused by regenerating your account token.
</Typography> </Typography>
</Grid2> </Grid2>
<Grid2 container sx={{ flexGrow: 1, p: 1 }} alignItems="center"> <Grid2 container sx={{ flexGrow: 1, p: 1 }} alignItems="center">
<Typography> <Typography>
Alternatively, you can just <code>zrok disable</code> any enabled environments and re-enable Keep in mind that once you've regenerated your account token, any running <code> zrok share </code>
using the updated account token. Running <code>zrok disable</code> before you regenerate will or <code> zrok access </code> processes may not be able to interact with the zrok service properly
until they are restarted.
</Typography>
</Grid2>
<Grid2 container sx={{ flexGrow: 1, p: 1 }} alignItems="center">
<Typography>
Alternatively, you can just <code> zrok disable </code> any enabled environments and re-enable
using the updated account token. Running <code> zrok disable </code> before you regenerate will
delete your environments and any shares they contain (including reserved shares). So if you have delete your environments and any shares they contain (including reserved shares). So if you have
environments and reserved shares you need to preserve, your best option is to update the <code>zrok_token</code> in environments and reserved shares you need to preserve, your best option is to use the
those environments as described above. <code> zrok rebase accountToken </code> command as described above.
</Typography> </Typography>
</Grid2> </Grid2>
{ successMessage ? null : controls } { successMessage ? null : controls }