mattermost / mattermost/mattermost-plugin-cloud
long running instances
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
most of the time, we create an instance to test a feature and forget to destroy after some time. Since this can happen a lot, i'd suggest a couple of options to prevent/minimize it:
- daily alert on running instances
- TTL option (i'd say with a couple of days of default) that will terminate the instance after a while. it would be great if it would issue a DM reminding that it will be destroyed some time before that happens if there is an option to extend it.
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
No files, tests, or entry points are named. Start by locating the instance lifecycle and notification entry points, then clarify whether daily alerts, TTL termination, pre-expiry direct messages, and TTL extension are all required. Done should include agreed behavior for each option and tests covering the lifecycle and reminders.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100