Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

auto-create missing secrets on deploy #453

Open
mrferris opened this issue Jun 8, 2021 · 1 comment
Open

auto-create missing secrets on deploy #453

mrferris opened this issue Jun 8, 2021 · 1 comment
Labels
PRIORITY: Low Nice to have feature, or easy work around TRIAGE: Accepted Ticket has been accepted for work to proceed TYPE: Enhancement New behaviour or feature

Comments

@mrferris
Copy link
Contributor

mrferris commented Jun 8, 2021

Edge case that we do want to handle from genesis #275
@mrferris mrferris mentioned this issue Jun 8, 2021
Closed
@dennisjbell
Copy link
Member

This should only be done when the repo has a secrets provider set. If they are using legacy mode where is just uses the system's safe target, it should still error out in case the target is wrong.

@mrferris mrferris added TRIAGE: Accepted Ticket has been accepted for work to proceed TYPE: Enhancement New behaviour or feature PRIORITY: Low Nice to have feature, or easy work around labels Jun 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
PRIORITY: Low Nice to have feature, or easy work around TRIAGE: Accepted Ticket has been accepted for work to proceed TYPE: Enhancement New behaviour or feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dennisjbell @mrferris