Skip to content

Feature request: Add the ability to designate a 'prod' environment, switch to another after N minutes of idle #88

@drosenbauer

Description

@drosenbauer

It's easy to forget that you've got your VSCode instance pointed at a sensitive environment and accidentally overwrite a role or something in Prod that you didn't mean to. (Of course, the better practice is to never use VSCode to push to Prod, but sometimes it's just easier to do this for non-code-y things like roles and workgroups and capabilities.)

I'd like to add a new feature that:

  • Lets you designate one or more sensitive environments via plugin settings
  • Lets you designate a safe environment (or none)
  • After N minutes without any interaction with the connected system, switch to the safe environment and alert the user

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions