-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
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
Add a fetch
seed_type
#45
Comments
This was referenced Jul 9, 2023
6 tasks
jkomoros
added a commit
that referenced
this issue
Jul 22, 2023
This will allow it to be used for local fetches. Part of #45.
jkomoros
added a commit
that referenced
this issue
Jul 22, 2023
jkomoros
added a commit
that referenced
this issue
Jul 22, 2023
jkomoros
added a commit
that referenced
this issue
Jul 22, 2023
…t and a domain it asks the user if they want to allow it. Part of #45.
jkomoros
added a commit
that referenced
this issue
Jul 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Allows fetching from a remote origin. This is the primary way to get things in and out. It's also dangerous!
Fetches from seeds from local seed packets should be allowed, but the first time a remote seed fetches from a given URL, the user should get a chance to confirm (with a 'allow from now on'). The profile should store which seed packet locations the user has allowed to remember which ones need a confirmation.
The fetch should allow configuring subsubset of
fetch
parameters.Having an ability to store a secret store for a seed packet that only it can reference would be useful for API keys for fetch that the library isn't aware of for its own use.
property
seed type should work for dotted gets so it's possible to traverse into themjson
(default), string)disallow_fetch
protected propertyThe text was updated successfully, but these errors were encountered: