We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
My platform starts up a new container for each build and I keep loosing write permissions.
In the dat-sdk, is it possible to:
I was thinking of something like:
const myArchive = await DatArchive.create({ title: 'My Archive' }) const archive = await DatArchive.load(myArchive.url, {secretKey: myArchive.secretKey})
That way, I can set secretKey as an env variable, and maintain write permissions between containers.
secretKey
The text was updated successfully, but these errors were encountered:
Would you be comfortable with an API like 'archive.getSecretKey()` which returns a promise?
cc @pfrazee since this might be a divergence from Beaker's API.
Sorry, something went wrong.
Sure go ahead
Cool, I might get to it next week, but in the meantime a PR with a unit test would be very much welcome. It could look something like
async getSecretKey() { await this._loadPromise return this._archive.secretKey }
671ef24
No branches or pull requests
My platform starts up a new container for each build and I keep loosing write permissions.
In the dat-sdk, is it possible to:
I was thinking of something like:
That way, I can set
secretKey
as an env variable, and maintain write permissions between containers.The text was updated successfully, but these errors were encountered: