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

add a flag to pass email address into solo context connect #950

Open
Tracked by #588
jeromy-cannon opened this issue Dec 9, 2024 · 0 comments · May be fixed by #993
Open
Tracked by #588

add a flag to pass email address into solo context connect #950

jeromy-cannon opened this issue Dec 9, 2024 · 0 comments · May be fixed by #993
Assignees
Labels
Internal Requirement Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. P1 High priority issue. Required to be completed in the assigned milestone.

Comments

@jeromy-cannon
Copy link
Contributor

jeromy-cannon commented Dec 9, 2024

  • add a flag to pass email address into solo context connect

when I ran the following:

solo init
solo context connect -n jeromy-solo --context gke-fullstack --cluster-name gke_hedera-automation_us-central1_fullstack-test-edge

it prompted me for an email address. but, there is no option listed under help:

solo context connect --help
 context connect

updates the local configuration by connecting a deployment to a k8s context

Options:
      --dev           Enable developer mode                                                                    [boolean]
  -q, --quiet-mode    Quiet mode, do not prompt for confirmation                                               [boolean]
  -c, --cluster-name  Cluster name                                                                              [string]
      --context       The Kubernetes context name to be used                                                    [string]
  -f, --force         Force actions even if those can be skipped                                               [boolean]
  -n, --namespace     Namespace                                                                                 [string]
  -h, --help          Show help                                                                                [boolean]
  -v, --version       Show version number                                                                      [boolean]
@jeromy-cannon jeromy-cannon added P1 High priority issue. Required to be completed in the assigned milestone. Internal Requirement Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. labels Dec 9, 2024
@Ivo-Yankov Ivo-Yankov linked a pull request Dec 17, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Internal Requirement Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. P1 High priority issue. Required to be completed in the assigned milestone.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants