What's the reasoning behind not allowing read-only access to Stash during a backup? Seems like allowing a fetch/pull shouldn't be an issue.
Is this simply that the API exposed from Stash isn't differentiating between services that modify Stash and/or Git from those that only need to perform some type of read operation?
Stash needs to ensure that the database and the filesystem are both readonly for the duration of the backup to guarantee a consistent 'snapshot'. The plugin system is great and very flexible, but is makes it very hard to guarantee that nothing is modifying the database while the backup is being performed. For this reason, all access to the database is blocked during backup.
This means that Stash can't authenticate users during backup and as a result we can't provide readonly access to the repositories.
Hope that clarifies it!
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot