Skip to content
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

Open
7 of 10 tasks
jkomoros opened this issue Jul 8, 2023 · 0 comments
Open
7 of 10 tasks

Add a fetch seed_type #45

jkomoros opened this issue Jul 8, 2023 · 0 comments

Comments

@jkomoros
Copy link
Owner

jkomoros commented Jul 8, 2023

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 them

  • Add a fetch for remote URLs
  • Headers
  • Body
  • (other parameters)
  • format (json (default), string)
  • Add a fetch for local / relative URLs (if it needs to be supported differently)
  • Add disallow_fetch protected property
  • An option to not throw for http errors and instead pass back a string
  • When a seed from a remote packet initiates a fetch, ask the first time.
  • Filesystem profile should persist locations
jkomoros added a commit that referenced this issue Jul 22, 2023
jkomoros added a commit that referenced this issue Jul 22, 2023
If set to true, fetch will fail.

Part of #53. Part of #45.
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
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
For now it's just a simple version check, but soon it will have other things.

Part of #14. 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
jkomoros added a commit that referenced this issue Jul 22, 2023
Change the regular expression to just match everything between curly braces.

This makes a template of `{{data|json}}` to match across multi-line JSON work (test added).

Part of #17. Part of #45.
jkomoros added a commit that referenced this issue Jul 22, 2023
This is effectively a workaround for json template extraction being broken (#59).

Part of #45.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant