GUI: allow declaring API tokens read-only during creation

Open
#528 6 comments 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 14 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python

Research direction

The request is to add a read-only option when creating API tokens in the GUI, for least-privilege CI use such as terraform plan. Start from the existing token-creation UI and the token API, and from related issue #347, to see whether a read-only flag already exists on the backend. Done when a token can be created as read-only from the GUI and that token cannot perform writes.

Written by the indexing model from the issue text.

Description

enhancement gui help wanted

It would be useful to have a capability for read-only API tokens.

The use case I have is that we'd like to check if all values are up to date via terraform plan -detailed-exitcode || fail as part of a CI job. At the moment that could only be done by giving that CI job a token with read/write access.

This is a "least authority" concern similar to #347.

Dominant language
Python
Stars
678
Forks
74
Avg merge
7d 23h
Merged PRs (30d)
1

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from desec-io/desec-stack

All issues in desec-io/desec-stack

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.