Skip to content

Conversation

@consideRatio
Copy link
Member

@consideRatio consideRatio commented Nov 14, 2025

This PR depends on 2i2c-org/jupyterhub-groups-exporter#41 and has also been tested together with it.


In panels related to storage, we try to map directory names to the usernames that they were created for.

We want to support mapping [email protected] as a username to either my-2ename-40example-2ecom or my-name-example-com---abcd1234, and previously we only mapped my-2ename-40example-2ecom, but with this
change we could map also my-name-example-com---abcd1234 to the username.

actual username:          [email protected]
legacy scheme ("escape"): my-2ename-40example-2ecom
modern scheme ("safe"):   my-name-example-com---abcd1234

This requires version >= 1.2.0 of jupyterhub-groups-exporter, where the username_safe label is available, but it won't error without it.

In panels related to storage, we try to map directory names to the
usernames that they were created for.

We want to support mapping `[email protected]` as a username to either
`my-2ename-40example-2ecom` or `my-name-example-com---abcd1234`, and
previously we only mapped `my-2ename-40example-2ecom`, but with this
change we could map also `my-name-example-com---abcd1234` to the
username.

```
actual username:          [email protected]
legacy scheme ("escape"): my-2ename-40example-2ecom
modern scheme ("safe"):   my-name-example-com---abcd1234
```

This requires version >=1.2.0 of jupyterhub-groups-exporter where
the `username_safe` label is available, but won't error without it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant