Summary
Add support for passing a PEM file path directly to all secret-related commands in this module.
Scope
This should apply to all functions ending with Secret, including settings secret functions.
Problem
Right now, certificate-based secret workflows require manual preprocessing of PEM contents before calling secret commands. That adds friction and increases the risk of mistakes in CI/CD automation.
Proposed behavior
Allow users to provide a PEM file path (for example via a -PemFile parameter), and let each relevant command handle reading and formatting internally.
Why this helps
- Simplifies secret management automation
- Reduces boilerplate in scripts and pipelines
- Makes certificate-based secret workflows easier to adopt consistently across all secret commands
Acceptance criteria
- Every command in the module that ends with
Secret supports direct PEM file input
- Settings secret functions are included
- Clear validation/error messages for missing/invalid PEM files
- Help/examples updated to show PEM usage across secret commands
Summary
Add support for passing a PEM file path directly to all secret-related commands in this module.
Scope
This should apply to all functions ending with
Secret, including settings secret functions.Problem
Right now, certificate-based secret workflows require manual preprocessing of PEM contents before calling secret commands. That adds friction and increases the risk of mistakes in CI/CD automation.
Proposed behavior
Allow users to provide a PEM file path (for example via a
-PemFileparameter), and let each relevant command handle reading and formatting internally.Why this helps
Acceptance criteria
Secretsupports direct PEM file input