certimate-go / certimate-go/certimate
[Feature] Deploy: Use certificate or workflow name as filename
- Dominant language
- Go
- Stars
- 9.3k
- Forks
- 898
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 8
Description
### Description / 功能描述
Hello,
when you create a workflow and configure the deploy node to do store the certificate on the local filesystem (Localhost), the default path is always "/etc/ssl/certimate/cert.[key,pfx,crt,...]" (v0.4.20). It would be nice if the default were the domain name of the certificate, or at least the workflow name. If multiple domains are listed in the certificate, the first one could be used as the "main domain" for that certificate, just like LetsEncrypt handles it.
### Motivation / 请求动机
I am storing the certificates in PFX format to a folder. I have to manually change the path for each workflow and it is very easy to forget to rename a certificate. Since you have to select the certificate (Application) anyways for the deploy node, it would be nice to have it automatically set the filename for the certificate according to the domain.
### Miscellaneous / 其他
_No response_
### Contribution / 贡献代码
- [ ] I am interested in contributing a PR for this! / 我乐意为此提交代码并发起 PR!
Contributor guide
Research direction
Start by tracing the deploy node's Localhost target and its default /etc/ssl/certimate/cert.* path. Check how the selected certificate exposes its domains and how the workflow name is available; done means the generated filename uses the intended domain or workflow fallback, including certificates with multiple domains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100