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

✨(gentest): allow custom headers in gentest config file and add an example config file #891

Closed
Tracked by #893 ...
raxhvl opened this issue Oct 14, 2024 · 0 comments · Fixed by #892
Closed
Tracked by #893 ...
Labels
scope:gentest Scope: Changes to gentest CLI command type:feat type: Feature

Comments

@raxhvl
Copy link
Contributor

raxhvl commented Oct 14, 2024

  1. Instead of using specific fields like client_id and secret, I propose we change the config file structure to include a single key called rpc_headers. This allows users to define a flexible number of headers as needed.
{
    "remote_nodes": [
        {
            "name": "mainnet_archive",
            "node_url": "https://abc.com",
            "rpc_headers": {
                "Authorization": "Bearer your_token_here",
                "Another-Header": "value"
            }
        }
    ]
}
  1. Create a config.json.example file that serves as a template for new users. This will help them quickly understand how to structure their configuration.
@danceratopz danceratopz changed the title ✨ Allow custom headers in gentest config file and add an example config file ✨(gentest): allow custom headers in gentest config file and add an example config file Oct 15, 2024
@danceratopz danceratopz added type:feat type: Feature scope:gentest Scope: Changes to gentest CLI command labels Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope:gentest Scope: Changes to gentest CLI command type:feat type: Feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants