Skip to content

[FEATURE] Add a shortcut for creating secrets #519

Description

@edenreich

Summary

This CLI often needs API keys to connect to different providers.

The user doesn't need to remember which providers they have or what secrets they can put in the CLI.

The environment variables available for the secrets should be generated for the user.

Acceptance Criteria

  • There is a shortcut for secrets called /env
  • When this shortcut is executed a .env.example file is created - if not already exists
  • When executing /init in a project that doesn't have .env.example this is also created
  • The .env.example file contains all the different providers API environment variables (<PROVIDER>_API_KEY=)
  • If the .env.example already exists it throws an error letting the user know it's already exists
  • If the /init was executed the error doesn't affect the other generated files
  • If there is no .gitignore in the root of the project, it's being created and .env is placed
  • After successful execution of /env the user gets an hint what they should do next (cp .env.example .env)
  • it's documented
  • it's tested

Metadata

Metadata

Assignees

No one assigned

    Labels

    Fields

    No fields configured for Feature.

    Projects

    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions