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

deploytarget name on lagoon-get-environment #152

Closed
dasrecht opened this issue Sep 3, 2020 · 4 comments · Fixed by #362
Closed

deploytarget name on lagoon-get-environment #152

dasrecht opened this issue Sep 3, 2020 · 4 comments · Fixed by #362
Labels
enhancement New feature or request

Comments

@dasrecht
Copy link
Contributor

dasrecht commented Sep 3, 2020

Is your feature request related to a problem? Please describe.
It would be helpful to see the openshift/deploytarget a project is running on on the lagoon-get-project command

Describe the solution you'd like

ID  	PROJECTNAME	GITURL                                    	BRANCHES               	PULLREQUESTS	PRODUCTIONROUTE     	DEVENVIRONMENTS	DEVENVLIMIT	PRODUCTIONENV	AUTOIDLE    DeployTarget
1271	example   	git@github.com:example/example.git	^(dev|prod|release/.*)$	true        	https://example.net	5/5            	5          	prod         	1   us1-lagoon

Basically it would be the information from

    openshift {
      name
    }
@shreddedbacon
Copy link
Member

Is this section of the query available to all users? Adding this could be a permission issue if say developer role doesn't have permission to query this field.

@seanhamlin
Copy link
Collaborator

seanhamlin commented May 18, 2021

Keen for this as well, as I find Lagoon CLI quite nice in scripting, having to do GraphQL in cURL to emulate this, was certainly not ideal.

Perhaps hiding it behind a flag --show-cluster or something to deal with any permission issues.

@seanhamlin seanhamlin added the enhancement New feature or request label May 18, 2021
@bomoko
Copy link
Contributor

bomoko commented Oct 12, 2023

Discussing this in tech debt, perhaps the right level to surface this detail at is on the environment level, given that there are potentially many deploy target configs - the info may be somewhat misleading/a little useless depending on the setup.

@shreddedbacon shreddedbacon changed the title openshift/deploytarget name on lagoon-get-project openshift/deploytarget name on lagoon-get-environment Jan 4, 2024
@shreddedbacon shreddedbacon changed the title openshift/deploytarget name on lagoon-get-environment deploytarget name on lagoon-get-environment Jan 4, 2024
@seanhamlin
Copy link
Collaborator

This bit me again recently. The information is vastly different in the list command compared to the get command. Ideally (IMO) the list command simply lists all environments you have access to, but the information contained in each environment is no different from get.

Current workaround:

In order to get the current deployTarget, I need to query the list command, and then enumerate through each returned environment to see if the namespace matches. Not super ideal.

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

Successfully merging a pull request may close this issue.

4 participants