-
Notifications
You must be signed in to change notification settings - Fork 438
CNTRLPLANE-378: Move bootstrap apply bash into kas-bootstrap binary #5937
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
CNTRLPLANE-378: Move bootstrap apply bash into kas-bootstrap binary #5937
Conversation
|
@enxebre: This pull request references CNTRLPLANE-378 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 story to target the "4.19.0" version, but no target version was set. DetailsIn 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: enxebre The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
cc @wking |
kas-bootstrap/main.go
Outdated
| ResourcesPath: "/work", | ||
| } | ||
| cmd.Flags().StringVar(&opts.RenderedFeatureGatePath, "rendered-featuregate-path", "", "The path to the rendered featureGate CR") | ||
| cmd.Flags().StringVar(&opts.ResourcesPath, "resources-path", "", "The path to the rendered featureGate CR to reconcile and all resources to apply") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: wording
| cmd.Flags().StringVar(&opts.ResourcesPath, "resources-path", "", "The path to the rendered featureGate CR to reconcile and all resources to apply") | |
| cmd.Flags().StringVar(&opts.ResourcesPath, "resources-path", "", "The path to the rendered featureGate CR to reconcile and apply all the resources.") |
b4d2f8e to
8e980c1
Compare
|
/lgtm |
Follow up for openshift#5871 It aims to alleviate the current bash scripts fragility and cover existing and any upcoming changes to this logic with appropriate test coverage
8e980c1 to
89066ea
Compare
|
@enxebre: This pull request references CNTRLPLANE-378 which is a valid jira issue. DetailsIn 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. |
|
/test e2e-aws |
|
/override "Red Hat Konflux / hypershift-operator-main-enterprise-contract / hypershift-operator-main" |
|
@enxebre: Overrode contexts on behalf of enxebre: Red Hat Konflux / hypershift-operator-main-enterprise-contract / hypershift-operator-main, Red Hat Konflux / hypershift-operator-main-on-pull-request DetailsIn 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 kubernetes-sigs/prow repository. |
|
/test e2e-aks |
|
@enxebre: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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 kubernetes-sigs/prow repository. I understand the commands that are listed here. |
616a2fa
into
openshift:main
|
[ART PR BUILD NOTIFIER] Distgit: hypershift |
This was introduced here openshift#5871 It shouldn't be needed now openshift#5937 is merged
This was introduced here openshift#5871 It shouldn't be needed now openshift#5937 is merged
This was introduced here openshift#5871 It shouldn't be needed now openshift#5937 is merged
What this PR does / why we need it:
Follow up for #5871
It aims to alleviate the current bash scripts fragility and cover existing and any upcoming changes to this logic with appropriate test coverage
Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)format, where issue_number might be a GitHub issue, or a Jira story:Fixes #
Checklist