Feat: Add support for saving and exporting existing service templates
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
Right now, I create multiple services with many similar configurations, and I'm forced to copy and paste from one service to another. General management would be nice.
In principle, a better way to import and export templates would be enough.
Describe the solution you'd like
- In the Advanced tab, under Import, add an export button in JSON and Base64.
- Add a save locally button. Then, instead of importing with Base64, you could select from the saved templates.
Describe alternatives you've considered
I considered implementing my template system and using the Base URL in the "Create from Templates" section, but it represents maintaining a new service for a few templates.
Additional context
No response
Will you send a PR to implement it?
Maybe, need help
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Advanced tab's current Base64 import flow and the Create from Templates section. Define how existing service configurations are serialized to JSON and Base64, saved locally, and selected for import. Done means users can export in both formats, save templates locally, and choose saved templates instead of pasting Base64.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100