Support self-managed instances for agent connect command

In Provide connect command for agent cluster (#463769 - closed) we've introduced in a new modal that shows a glab command to connect to an agent. However, that command doesn't account for self-managed GitLab instances.

To support those the GITLAB_HOST environment variable must be set properly for glab to connect to the proper host.

Implementation guide

1. Update connect_to_agent_modal
2. Add the GITLAB_HOST=${currentHost} part at the beginning of the command in case it's not gitlab.com
3. Update the corresponding tests.

added featureaddition groupenvironments workflowscheduling labels

set weight to 1

marked this issue as related to #463769 (closed)

added typefeature label

added devopsdeploy sectioncd labels

cc @anna_vovchenko

Thanks for opening an issue, @timofurrer! Does this updated command look correct (it will only add the host part if it's not gitlab.com)?

@anna_vovchenko Yes, exactly

is it okay/possible to compute the currentHost value from window.location.host?

from !171865 (comment 2199474742)

It might be worth considering using gon.gitlab_url here, as it represents the canonical URL set by the server. This approach could also simplify testing.

Thanks for working on this, @MatteoAxelle! I’ll go ahead and assign the issue to you since you're actively working on it.

changed milestone to %Backlog

added frontend label

mentioned in issue gitlab-org/quality/triage-reports#19283 (closed)

changed the description

added Seeking community contributions quick win labels

mentioned in issue gitlab-org/quality/triage-reports#19367 (closed)

mentioned in merge request !163969 (closed)

assigned to @Deepak18-06

removed Seeking community contributions label

mentioned in issue gitlab-org/quality/triage-reports#19538 (closed)

mentioned in issue gitlab-org/quality/triage-reports#19653 (closed)

mentioned in issue gitlab-org/quality/triage-reports#19665 (closed)

mentioned in issue gitlab-org/quality/triage-reports#19802 (closed)

mentioned in issue gitlab-org/quality/triage-reports#19912 (closed)

mentioned in issue gitlab-org/quality/triage-reports#19992 (closed)

mentioned in issue gitlab-org/quality/triage-reports#20125 (closed)

mentioned in issue gitlab-org/quality/triage-reports#20243 (closed)

mentioned in issue gitlab-org/quality/triage-reports#20325 (closed)

mentioned in issue gitlab-org/quality/triage-reports#20441 (closed)

mentioned in issue gitlab-org/quality/triage-reports#20578 (closed)

mentioned in merge request !171865 (merged)

mentioned in issue gitlab-org/quality/triage-reports#20746 (closed)

added Community contribution label

assigned to @MatteoAxelle and unassigned @Deepak18-06

added workflowin review label and removed workflowscheduling label

changed milestone to %17.6

mentioned in issue gitlab-org/ci-cd/deploy-stage/environments-group/general#97 (closed)

changed milestone to %17.7

mentioned in issue gitlab-org/quality/triage-reports#20826 (closed)

Closing the issue as the related MR is done and deployed to production.

Thanks for your contribution, @MatteoAxelle!

added workflowcomplete label and removed workflowin review label

closed