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

API status and Quota commands should handle --instance option #406

Closed
elacaille18 opened this issue Oct 26, 2022 · 2 comments
Closed

API status and Quota commands should handle --instance option #406

elacaille18 opened this issue Oct 26, 2022 · 2 comments
Labels
type:feature Feature request

Comments

@elacaille18
Copy link
Contributor

Is your feature request related to a problem? Please describe.

I have configured my ggshield with different GitGuardian instances:

  • GitGuardian SAAS dashboard.gitguardian.com (the default one)
  • my GitGuardian on prem instance
    However when trying to know the API status or the quota for both instances, it is impossible to specify which instance I want. It always gives the GG SAAS info

Describe the solution you'd like

API status and quota commands should support the --instance option. Just like the ggshield auth and ggshield config command

Describe alternatives you've considered

None. No workaround found

@elacaille18 elacaille18 added the type:feature Feature request label Oct 26, 2022
@elacaille18 elacaille18 changed the title API status and Quota command should handle instance option API status and Quota command should handle --instance option Oct 26, 2022
@elacaille18 elacaille18 changed the title API status and Quota command should handle --instance option API status and Quota commands should handle --instance option Oct 26, 2022
@agateau-gg
Copy link
Collaborator

Looks like a duplicate of #359. Can I close it as such?

@agateau-gg
Copy link
Collaborator

Closing as duplicate of #359.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature Feature request
Projects
None yet
Development

No branches or pull requests

2 participants