Skip to content

Allow post-deployment connections straight from graph files#814

Closed
sr-gi wants to merge 1 commit into
bitcoin-dev-project:mainfrom
sr-gi:2026-07-post-deploy-connections
Closed

Allow post-deployment connections straight from graph files#814
sr-gi wants to merge 1 commit into
bitcoin-dev-project:mainfrom
sr-gi:2026-07-post-deploy-connections

Conversation

@sr-gi

@sr-gi sr-gi commented Jul 6, 2026

Copy link
Copy Markdown
Member

Allows creating connections from a graph file other than manual. This connections are created after deployment using the addconnection (test-only) RPC.

Connections are stored under a new tag in the graph files: addconnection. If any of this tags is found, the scenario is run right after deployment to create those connections. Otherwise, this is a noop.

Graph file entry example:

nodes:
- addnode:
    - tank-0015
    - tank-0013
    - tank-0005
    - tank-0006
    - tank-0019
    - tank-0014
    - tank-0004
    - tank-0021 
- addconnection:
    - tank-0010
    - tank-0020

Disclaimer: addconnection.py has been highly vibecoded. Happy to trim it down or re-work it.

@sr-gi sr-gi force-pushed the 2026-07-post-deploy-connections branch from 219761d to 1c202d6 Compare July 6, 2026 12:02
Allows creating connections from a graph file other than manual.
This connections are created after deployment using the addconnection (test-only)
RPC.

Connections are stored under a new tag in the graph files: addconnection. If any
of this tags is found, the scenario is run right after deployment to create those
connections. Otherwise, this is a noop.

Graph file entry example:

nodes:
- addnode:
  - tank-0015
  - tank-0013
  - tank-0005
  - tank-0006
  - tank-0019
  - tank-0014
  - tank-0004
  - tank-0021
  addconnection:
  - tank-0010
  - tank-0020
@pinheadmz

Copy link
Copy Markdown
Contributor

This is cool, it's a feature I want, but I'm starting my own branch here: #815

The syntax in network.yaml might end up being slightly different

@sr-gi

sr-gi commented Jul 7, 2026

Copy link
Copy Markdown
Member Author

SGTM, happy to adapt to the format you decide on downstream when merged.

I'm currently running my patch downstream, but I'm also happy to ditch that one and run yours so I can give some practical review feedback

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

Successfully merging this pull request may close these issues.

2 participants