process: add docs for adding readonly request access#130
process: add docs for adding readonly request access#130v9n wants to merge 5 commits intocanton-foundation:mainfrom
Conversation
762ffe6 to
f74b81f
Compare
|
Thanks @v9n |
They looks similar on the steps today, but the context is quite different IMHO.
I think let keep it separate, so we don't confused a newly user that is spinning up a validator. So we can keep that part clear, conscice and to the point. Adding less noise to that part is better. |
Co-authored-by: Itai Segall <itai.segall@digitalasset.com> Signed-off-by: Vinh <vinh@mailwip.com>
Co-authored-by: Itai Segall <itai.segall@digitalasset.com> Signed-off-by: Vinh <vinh@mailwip.com>
|
@v9n Can you make the changes directly? |
|
Hi @hythloda What change do I need to make to get this PR merge? I think Ital want some changes but I provided my though. let me ask Ital again. Hi @isegall-da Do you think this is good? or you still want to merge the section and insert the part where they are different? |
|
|
||
| Currently, only individual IPs are allowed, so you will need to explicitly write out multiple `/32` entries if you have a range. There isn't an official limit on how many IPs are allowed, but keep it fewer than three. | ||
|
|
||
| Unlike validator IPs, read-only access IP addresses can be reused across all network environments (**Dev**, **Test**, and **Main**). |
There was a problem hiding this comment.
| Unlike validator IPs, read-only access IP addresses can be reused across all network environments (**Dev**, **Test**, and **Main**). |
Outdated, that's allowed for validator IPs now too
| "<org-name> / <operator-name-or-sponsor-name>" : [ | ||
| "ip1/32", | ||
| "ip2/32" | ||
| ] | ||
| ``` | ||
|
|
||
| When the organization runs the node themselves, list the sponsor in the second part after the dash (/). |
There was a problem hiding this comment.
| "<org-name> / <operator-name-or-sponsor-name>" : [ | |
| "ip1/32", | |
| "ip2/32" | |
| ] | |
| ``` | |
| When the organization runs the node themselves, list the sponsor in the second part after the dash (/). | |
| "<org-name> / <sponsor-name>" : [ | |
| "ip1/32", | |
| "ip2/32" | |
| ] |
|
@v9n If you're fine with my proposed changes, can you just accept and we'll merge? I think it's good enough. |
Define an initial process to submit read-only ip access