Details
-
Suggestion
-
Resolution: Timed out
-
None
-
Ubuntu Linux 12.04.3, OpenJDK, Stash 2.8.2
Description
Hi everyone,
We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out.
Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bitbucket Server team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.
We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. If you're really passionate about this suggestion, please comment with your case in detail and we'll reconsider. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Thank you,
Imran Khan
Product Manager - Bitbucket Server and Data Center
While reviewing the Stash documentation I spotted the Stash Backup Client in the best practices for backups. I love the idea, but I'm not wild about having a SuperAdmin's credentials inside a crontab file on the server.
I wanted to throw out a request that a dedicated backup user be created that is restricted from actual logins and allowed read-only access to the critical bits.
It is superb that you guys have taken this important step into account and built in an integrated approach that can be bolted on by those who need it to take care of such a critical task.