You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting a project with the -p or --project flag, an error is returned:
pctl get clusters --project PROJECTNAME
Error: invalid flag/argument passed for project
Setting the project in the configuration file works as expected.
Steps to reproduce the bug
Find a valid project name
Run pctl get clusters --project PROJECTNAME
You will get an error
Are you using the latest version of the project?
You can check your version by running helm ls|grep '^<deployment-name>' or using pctl, pctl version, and provide the output.
pctl version
VERSION: 0.1.5
BUILD: 0.1.5
BUILD-TIME: 1703220028
ARCH: linux/amd64
What is your environment setup? Please tell us your cloud provider, operating system, and include the output of kubectl version --output=yaml and helm version. Any other information that you have, eg. logs and custom values, is highly appreciated!
Running pctl on fedora Linux connecting to a paralus cluster on Exoscale SKS running the latest paralus release.
(optional) If you have ideas on why the bug happens or how it can be solved, please provide it here
I've described the bug, included steps to reproduce it, and included my environment setup with all customizations.
I'm using the latest version of the project.
The text was updated successfully, but these errors were encountered:
Expected vs actual behavior
-p
or--project
flag, an error is returned:Setting the project in the configuration file works as expected.
Steps to reproduce the bug
pctl get clusters --project PROJECTNAME
Are you using the latest version of the project?
You can check your version by running
helm ls|grep '^<deployment-name>'
or using pctl,pctl version
, and provide the output.What is your environment setup? Please tell us your cloud provider, operating system, and include the output of
kubectl version --output=yaml
andhelm version
. Any other information that you have, eg. logs and custom values, is highly appreciated!Running pctl on fedora Linux connecting to a paralus cluster on Exoscale SKS running the latest paralus release.
(optional) If you have ideas on why the bug happens or how it can be solved, please provide it here
The text was updated successfully, but these errors were encountered: