Skip to content

Documentation on SECRETS is insufficient #60

@pboling

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.

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