Repository navigation
Conversation
LLMs reach for --local-file far more often than --local-path, so expose the former and keep the latter as a hidden alias. Applied to install, get-config and plan so help text is consistent. Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
This comment has been minimized.
This comment has been minimized.
Expose --kubeconfig (with -k) as the flag for the kubeconfig
file path on install, get-config, and plan, matching the name
every k8s tool and our own ready command use. Keep --local-file
and --local-path as hidden aliases so existing scripts keep
working.
Also create ~/.kube and touch the config file when missing in
install and get-config, matching k3sup-pro so a fresh machine
no longer fails with "no such file or directory".
Fix k3s-channel help ("or i.e. v1.19") and datastore help
("connection-string").
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
This comment has been minimized.
This comment has been minimized.
--local-file was added in this PR and never released, and is superseded by --kubeconfig, so remove it from install, get-config and plan. Keep --kubeconfig visible and --local-path as the hidden compatibility alias. Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
This comment has been minimized.
This comment has been minimized.
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
AI Pull Request OverviewDisclaimer: This review was generated by automated AI and may contain errors. Do not trust its outputs without human verification. Summary
Approval rating (1-10)6/10. The CLI changes look reasonable, but the workflow action refs appear to break both build and release automation. Summary per fileSummary per file
Overall AssessmentThe Go changes are narrowly scoped and mostly align with the PR goal: the new flag name is exposed consistently, the old flag remains available as a hidden alias, and missing kubeconfig directories are handled before writes and merges. The blocking concern is the workflow update to Detailed ReviewDetailed ReviewFindingsHigh: GitHub Actions refs appear to point at non-existent major versionsFiles: Both workflows now reference Use published action major versions instead, for example: - uses: actions/checkout@v4
- name: Install Go
uses: actions/setup-go@v5If the repository intentionally depends on newer major versions, pin to confirmed existing tags rather than speculative version numbers. Other Reviewed ChangesNo blocking findings in the scoped Go command changes. The shared AI agent details. |
Summary
--kubeconfig(with-k) as the flag for the kubeconfig file path on install, get-config, and plan, matching the name every k8s tool and our ownreadycommand use.--local-pathas a hidden compatibility alias.~/.kubeand touch the config file when missing in install and get-config, matching k3sup-pro so a fresh machine no longer fails with "no such file or directory".k3s-channelhelp ("or i.e. v1.19") anddatastorehelp ("connection-string").Testing
Verified live in a Slicer VM with a wiped
~/.kube:--kubeconfig,-k, and the hidden--local-pathall create the file.planemits--kubeconfigin its generated install script. Fullgo test ./...green, gofmt clean.