-
Notifications
You must be signed in to change notification settings - Fork 27
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
RHTAP-4048: rhtap-cli config
#485
base: main
Are you sure you want to change the base?
Conversation
@otaviof: This pull request references RHTAP-4048 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.19.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: otaviof The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
1 similar comment
/retest |
This change allows all cluster administrators to rely on a single configuration. Introduces the `rhtap-cli config` subcommand, responsible for managing a unique installer's configuration in the cluster. The configuration is then used from the cluster for all other subcommands, thus it becomes the first step on deploying RHTAP.
|
/retest |
1 similar comment
/retest |
@otaviof: The following test has Failed, say /retest to rerun failed tests.
Inspecting Test ArtifactsTo inspect your test artifacts, follow these steps:
mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/rhtap-team/rhtap-cli:e2e-4.16-z2qsb Test results analysis<not enabled> |
This change allows all cluster administrators to rely on a single configuration.
Introduces the
rhtap-cli config
subcommand, responsible for managing a unique installer's configuration in the cluster.The configuration is then used from the cluster for all other subcommands, thus it becomes the first step on deploying RHTAP.