Update pipelineServer

[pnaik1]

Closes: #1214

Description

Allow for a prefill from a Data Connection for reuse of data that have already setup
separating the relationship between the Data Connection & the DSPA.

Screencast.from.2023-09-13.18-52-30.webm

3. the view pipeline server
   
4. Modified the alert info in the configure pipeline modal

4) The dropdown with bucket whenever available

How Has This Been Tested?

1. create a pipeline Server
2. check for the prefill dataconnection dropdown ( note the dropdown appears only when the data connection are present)
3. check whether the pipeline server is configured correctly
4. check the view pipeline server whether the data are correctly displayed

Test Impact

no test coverage

Request review criteria:

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

• Included any necessary screenshots or gifs if it was a UI change.
• Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

• The developer has tested their solution on a cluster by using the image produced by the PR to main

[pnaik1]

cc @yannnz

[Gkrumbach07]

The dropdown is heavily squished and is missing padding visible in the mockups

[Gkrumbach07]

There are some UX inconsistencies in the color and weight of the non-hidden credentials

vs

The keys should be bold and the text should not be grayed

[pnaik1]

The dropdown is heavily squished and is missing padding visible in the mockups
@Gkrumbach07
Just to confirm , so I can give the width properly
I agree need some width for this , but i was wondering at the screenshot you shared is it looking too squished?
My cluster is looking like this

[Gkrumbach07]

small nit

these are all greyed instead of a pure black. is this intended, because the mocks shwo them as black not grey

[Gkrumbach07]

Just to confirm , so I can give the width properly
I agree need some width for this , but i was wondering at the screenshot you shared is it looking too squished?
My cluster is looking like this

Tested again and it looks like you fixed the padding issues and the width is correct now

[Gkrumbach07]

bucket is not pulled from the data connection or shown in the dropdown menu. is this intended?

[pnaik1]

bucket is not pulled from the data connection or shown in the dropdown menu. is this intended?

@Gkrumbach07 referring to the Mock https://www.sketch.com/s/6c72b6b2-2c32-45ff-b07c-381d9d8c8267/a/JAamzrb , the dropdown doesnot have bucket in the list

[Gkrumbach07]

@Gkrumbach07 referring to the Mock https://www.sketch.com/s/6c72b6b2-2c32-45ff-b07c-381d9d8c8267/a/JAamzrb , the dropdown doesnot have bucket in the list

sounds good

/lgtm

[andrewballantyne]

If they have a bucket in their list, please use it. There is no reason to make them type that again.

[Gkrumbach07]

/lgtm

[DaoDaoNoCode]

Just a small text issue, otherwise it looks good.

[pnaik1]

@DaoDaoNoCode Thanks , I have made the changes

[DaoDaoNoCode]

/lgtm

[alexcreasy]

Hey @pnaik1 - you haven't checked the box to show it's been tested with an image on a cluster, has this been done?

[pnaik1]

@alexcreasy tested the image in the cluster and localy both are working fine

[alexcreasy]

Works well, looks good, thanks for rebasing and verifying this works deployed on a cluster.

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alexcreasy, DaoDaoNoCode, xianli123

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [alexcreasy]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment