Skip to content

Environment tokens should be able to be managed from the nil environment #870

Open
@ezekg

Description

This would remove the requirement that all environments must have an admin, which results in a confusing DX because those admins must be unique i.e. you end up with admins like john@example.com and john+ci@example.com, and that gets hard to remember when switching environments. This would also let us implement environments in the current UI.

Instead, you could create an isolated environment using an admin token, and then generate an environment token for it after creation, and then immediately utilize the new environment; vs the current behavior of creating the environment with an admin, logging in as the new environment's admin, then using the new admin's token to generate an environment token, and then finally using the new environment token to utilize the environment.

The simpler approach above is currently how shared environments work (since a global admin is allowed to manage it), but isolated environments are convoluted right now and I think it could be simplified.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions