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.

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

Multiple input Secrets? #245

Closed
mihaigalos opened this issue Apr 30, 2024 · 6 comments
Closed

Multiple input Secrets? #245

mihaigalos opened this issue Apr 30, 2024 · 6 comments
Labels
enhancement New feature or request good first issue Good for newcomers Stale

Comments

@mihaigalos
Copy link
Contributor

Running v3.0.0, we have the problem of not being able to input multiple Secrets for generating SealedSecrets.
Any chance to support this for the future?

I mean the output doesn't have to be sealed in 1 go. It can be sealed for each secret and the output concatenated to the result.

@bakito
Copy link
Owner

bakito commented Apr 30, 2024

Hi @mihaigalos
No there are currently no plans for this.

@mihaigalos
Copy link
Contributor Author

Okok, no problem. Do you think I could have a look and potentially implement this?

@bakito bakito added enhancement New feature or request good first issue Good for newcomers labels Apr 30, 2024
@bakito
Copy link
Owner

bakito commented May 3, 2024

Would you be willing to create a pull request?

@mihaigalos
Copy link
Contributor Author

Had a deeper look, seems the bitnami kubeseal implementation can handle slices.

So this means the input can be multiple kind: Secret, if I understand correctly - at least from kubeseal's point of view.

@mihaigalos
Copy link
Contributor Author

Also, seems the problem comes from unsealing not sealing per se, because it cannot unseal a multi-yaml input..

Copy link

github-actions bot commented Jul 3, 2024

This issue has been inactive for 60 days. If the issue is still relevant please comment to re-activate the issue. If no action is taken within 7 days, the issue will be marked closed.

@github-actions github-actions bot added the Stale label Jul 3, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers Stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants