Act as user instead of service

[aktech]

Reference Issues or PRs

This is so that we have better control of fine-grained permissions on what a user can and cannot do instead of delegating these tasks to service, which has more permissions than user. Previously we were doing all the operations as service, this PR is undoing that.

What does this implement/fix?

Put a x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

Documentation

Access-centered content checklist

Text styling

• The content is written with plain language (where relevant).
• If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
• All links describe where they link to (for example, check the Nebari website).
• This content adheres to the Nebari style guides.

Non-text content

• All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
• If there are emojis, there are not more than three in a row.
• Don't use flashing GIFs or videos.
• If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
jhub-apps	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 16, 2024 4:40pm
jhub-apps-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 16, 2024 4:40pm

[krassowski]

This looks like a very nice solution. I wonder what will be the overhead of using temporary tokens for each operations (after all they are added to database and commits are not free) but I suspect that this will be rather cheap.

[aktech]

This looks like a very nice solution. I wonder what will be the overhead of using temporary tokens for each operations (after all they are added to database and commits are not free) but I suspect that this will be rather cheap.

Yeah, ideally I would have preferred caching them and delete them after some delay, but didn't wanted to complicate logic until we know it's a problem in practice.