Skip to content

Conversation

@lf-
Copy link
Contributor

@lf- lf- commented Nov 19, 2025

Uses amazonka-s3, which auto discovers credentials.

Did some manual testing:

glean --tier test --db-root ~/glean backup myrepo/0 s3:mybucket/jade-test
glean --tier test --db-root ~/glean2 restore s3:mybucket/jade-test/myrepo.0

Configuration ~/.config/glean/server/test, though I think this doesn't actually matter?

{
    "backup": {
        "allowed": ["myrepo"],
        "location": "s3:mybucket/jade-test"
    },
    "restore": {
        "enabled": true
    }
}

This feature really needs some documentation (especially given I don't know if fb expected anyone external to immediately go and use it so it's probably in a wiki somewhere?); I would appreciate the docs that exist getting released, or I can maybe write some.

@netlify
Copy link

netlify bot commented Nov 19, 2025

Deploy Preview for fb-oss-glean ready!

Name Link
🔨 Latest commit 5da86a7
🔍 Latest deploy log https://app.netlify.com/projects/fb-oss-glean/deploys/695e7e90d4a5bd00084b9c6f
😎 Deploy Preview https://deploy-preview-615--fb-oss-glean.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Nov 19, 2025
@lf-
Copy link
Contributor Author

lf- commented Nov 19, 2025

Plan: review internally with @parsonsmatt tomorrow then will mark as ready for review.

@lf- lf- force-pushed the jade/push-rxvyovyvttvl branch from 94b7e54 to 4fc007a Compare November 21, 2025 00:58
@lf- lf- marked this pull request as ready for review November 21, 2025 01:00
@lf-
Copy link
Contributor Author

lf- commented Nov 21, 2025

Reviewed with @parsonsmatt: we had some unsafePerformIO which existed to ensure that fromPath could get called multiple times while sharing the same lazily discovered AWS.Env (as those may require network access to create; they're kind of expensive), which I fixed by making adding backups an IO operation.

The goal here is that you can throw out the Backend object in client code and it won't really matter, and that AWS credentials are only discovered if the user is actually using the AWS features.

It's now in a state I'm happy with, so please take a look! :)

@lf- lf- force-pushed the jade/push-rxvyovyvttvl branch from 4fc007a to 80d46de Compare November 21, 2025 01:14
Copy link
Collaborator

@simonmar simonmar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great! Thanks for the contribution.

@lf- lf- force-pushed the jade/push-rxvyovyvttvl branch 4 times, most recently from 1c05f2a to f2e22ef Compare November 25, 2025 00:46
@simonmar
Copy link
Collaborator

CI failure with 9.2.8

@lf- lf- force-pushed the jade/push-rxvyovyvttvl branch from f2e22ef to 79c5dfe Compare November 25, 2025 18:41
@lf-
Copy link
Contributor Author

lf- commented Nov 25, 2025

CI failure with 9.2.8

Fixed it :) Not surprised I got got by developing on the officially unsupported 9.10.x

@lf- lf- force-pushed the jade/push-rxvyovyvttvl branch 3 times, most recently from 62d547b to 7fa2a04 Compare December 10, 2025 19:13
Uses amazonka-s3, which auto discovers credentials.

Did some manual testing:

```
glean --tier test --db-root ~/glean backup myrepo/0 s3:mybucket/jade-test
glean --tier test --db-root ~/glean2 restore s3:mybucket/jade-test/myrepo.0
```

Configuration ~/.config/glean/server/test, though I think this doesn't
actually matter?

```
{
    "backup": {
        "allowed": ["myrepo"],
        "location": "s3:mybucket/jade-test"
    },
    "restore": {
        "enabled": true
    }
}
```

This feature really needs some documentation (especially given I don't
know if fb expected anyone external to immediately go and use it so it's
probably in a wiki somewhere?); I would appreciate the docs that exist
getting released, or I can maybe write some.
@lf- lf- force-pushed the jade/push-rxvyovyvttvl branch from 7fa2a04 to 5da86a7 Compare January 7, 2026 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants