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

quiet flag to allow for uninterrupted run of quickstart script #743

Closed
ehearneRedHat opened this issue Jul 8, 2024 · 2 comments
Closed
Assignees
Labels
area/tests Changes to tests only good first issue Good for newcomers kind/enhancement New feature or request

Comments

@ehearneRedHat
Copy link
Contributor

What:

quiet flag to be added to hack\quickstart-setup.sh such that it will allow for an uninterrupted run of the script.

This would mean deciding on whether we wish for the script to continue, if a DNS provider is to be used, and if multicluster setup should be allowed/denied by default. Also, deciding on what the use case for the quiet flag would be, such as for development or CI/CD , as it would give us a better picture of how we wish to implement.

How:

When implemented, the user could pass the quiet flag when running the script e.g. quiet=true ./hack/quickstart-setup.sh and the user wouldn't have to provide any other input to allow the script to run to completion.

@ehearneRedHat
Copy link
Contributor Author

@ehearneRedHat ehearneRedHat moved this from In Progress to Ready For Review in Kuadrant Jul 24, 2024
@ehearneRedHat
Copy link
Contributor Author

Closing as #744 is now closed .

@ehearneRedHat ehearneRedHat closed this as not planned Won't fix, can't repro, duplicate, stale Jul 26, 2024
@github-project-automation github-project-automation bot moved this from Ready For Review to Done in Kuadrant Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tests Changes to tests only good first issue Good for newcomers kind/enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant