Skip to content

Documentation on SECRETS is insufficient #60

Description

@pboling

We need examples of how to do a realistic set of secrets that are part of our build process.

For the PR Reivew Apps action this documentation exists here:
https://fly.io/docs/blueprints/review-apps-guide/#default-secrets-and-environment-variables

Please make it exist somewhere for the regular superfly/flyctl-actions/setup-flyctl action too.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

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