specify infrastructure field
complete
I
Interim Harrier
Please can improvements be made when using the specify infrastructure field during deployments. Currently the list is not sorted alphabetically can this be ordered in this may to make it easier to search. A further request would be to make this field searchable, giving the developer the ability to start typing and results come back, for example if a dev would type "sma" the drop down would filter alphabetically smapiv1 smapiv2 and so on and so on.
Log In
P
Pranay Kaikini
complete
This feature has now been delivered.
I
Interim Harrier
Hi, is there a update for this feature, initially 31st July was mentioned below.
Harness Engineering
this fiscal quarter
Canny AI
Merged in a post:
Seach option required for namespace/agents/repositories
E
Environmental Cuckoo
We have a huge list of namespaces/agents/repositories. Currently we can scroll and select required values, but harness should have a search option above each drop down list so user can search as well.
This post was marked as
in progress
Rohan Gupta
this fiscal quarter
This is forecasted for July 31st Delivery.
I
Interim Harrier
Hi, do you have a date for this?
P
Pranay Kaikini
next fiscal quarter
Rohan Gupta
Merged in a post:
Infra Should Not Be Listed If the Service Is Not In Scope
S
Sound Dolphin
BACKGROUND:
In Harness we have the ability to scope Infrastructure Definitions to specific services. Then in the UI when we run a pipeline, we need to select a service and select an infra definition.
HARNESS FIRST GEN:
In the pipeline after we select a service, it would only show infra definitions that have the service in its scope. Thus, it was very easy to know where the service can be deployed.
HARNESS NEXT GEN:
In the pipeline after we select a service, it shows all infra definitions. If we select an infra definition that doesn't have the service in its scope, it will allow us to run and then give an Error. This is frustrating and scary that we're deploying to the wrong production environment.
PROBLEM:
We have so many services that our engineers don't know which infra to select. We previously relied on the fact that it only showed valid infra definitions that have been scoped to the service.
REQUEST:
How can we add this functionality back?
I
Interim Harrier
Hi Rohan, what does long term mean? in our DVS environment we have over 150 infra defs. Having this sorted in a order and searchable isnt really a nice to have but critical as it will save each engineer during each deployment time.
Load More
→