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.

Sign up for GitHub

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

Jump to bottom

Implement non-interactive/partial interactive mode for tezos-setup-wizard #568

Open
itkach opened this issue Nov 16, 2022 · 0 comments
Open

Implement non-interactive/partial interactive mode for tezos-setup-wizard #568

itkach opened this issue Nov 16, 2022 · 0 comments
Assignees
@krendelhoff2

Comments

@itkach
Copy link
Contributor

itkach commented Nov 16, 2022

Clarification and motivation

It would facilitate scripting and copy-paste distribution of setup instructions if tezos-setup-wizard had a non-interactive mode

Acceptance criteria

  • Non interactive mode: take user input from the command line, fail with a instructive error message in case of errors or incomplete input
  • Partial interactive mode: take user input from the command line, drop into interactive mode on errors or in case of incomplete input (skipping wizard steps where input was given on the command line)
@krendelhoff2 krendelhoff2 added the in progress this issue is currently being worked on label Dec 22, 2022
@krendelhoff2 krendelhoff2 self-assigned this May 19, 2023
@krendelhoff2 krendelhoff2 removed the in progress this issue is currently being worked on label Jul 17, 2023
krendelhoff2 added a commit that referenced this issue Jul 17, 2023
@krendelhoff2
[Chore] Unify interactive queries in tezos-setup
622b20f 
Problem: Some interactive queries use step concept,
while others are done through `yes_or_no`. It's useful
to unify them by using steps only for logging
and for the #568 (non-interactive mode) issue.

Solution: Rewrite delete node data query using steps
instead of `yes_or_no`.
krendelhoff2 added a commit that referenced this issue Jul 17, 2023
@krendelhoff2
[Chore] Unify interactive queries in tezos-setup
8b6e652 
Problem: Some interactive queries use step concept,
while others are done through `yes_or_no`. It's useful
to unify them by using steps only for logging
and for the #568 (non-interactive mode) issue.

Solution: Rewrite delete node data query using steps
instead of `yes_or_no`.
krendelhoff2 added a commit that referenced this issue Aug 7, 2023
@krendelhoff2
[Chore] Unify interactive queries in tezos-setup
5b1748c 
Problem: Some interactive queries use step concept,
while others are done through `yes_or_no`. It's useful
to unify them by using steps only for logging
and for the #568 (non-interactive mode) issue.

Solution: Rewrite delete node data query using steps
instead of `yes_or_no`.
@krendelhoff2 krendelhoff2 mentioned this issue Sep 13, 2023
Merged
3 tasks
krendelhoff2 added a commit that referenced this issue Oct 18, 2023
@krendelhoff2
[Chore] Unify interactive queries in tezos-setup
166f307 
Problem: Some interactive queries use step concept,
while others are done through `yes_or_no`. It's useful
to unify them by using steps only for logging
and for the #568 (non-interactive mode) issue.

Solution: Rewrite delete node data query using steps
instead of `yes_or_no`.
krendelhoff2 added a commit that referenced this issue Oct 19, 2023
@krendelhoff2
[Chore] Unify interactive queries in tezos-setup
f2bdb0c 
Problem: Some interactive queries use step concept,
while others are done through `yes_or_no`. It's useful
to unify them by using steps only for logging
and for the #568 (non-interactive mode) issue.

Solution: Rewrite delete node data query using steps
instead of `yes_or_no`.
krendelhoff2 added a commit that referenced this issue Oct 19, 2023
@krendelhoff2
[Chore] Unify interactive queries in tezos-setup
1399094 
Problem: Some interactive queries use step concept,
while others are done through `yes_or_no`. It's useful
to unify them by using steps only for logging
and for the #568 (non-interactive mode) issue.

Solution: Rewrite delete node data query using steps
instead of `yes_or_no`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@krendelhoff2 krendelhoff2

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@itkach @krendelhoff2