[Feature Request]: Database Connection Environment Highlighting (Color Coding for Dev/Test/Prod)

[vitorsantos-commits]

What would you like to happen?

Current Situation
Currently, all database connections in the Metadata Perspective look identical regardless of the environment they point to. Users must rely solely on the connection name to distinguish between Development, Homologation (HML), and Production environments. This increases the risk of accidental execution of pipelines or transformations against the wrong environment.

Proposed Improvement
Add an optional "Environment Color" property to the Database Connection metadata.

Color Selection: Within the Database Connection dialog, allow users to pick a color (e.g., Green for Dev, Yellow for HML, Red for Prod).

UI Integration: * The connection name in the Metadata tree should have a background or foreground highlight with the selected color.

Ideally, when a pipeline using a "Red" (Production) connection is open, a small border or indicator could appear in the canvas to warn the user.

Expected Behavior
A user can quickly identify that postgres_data_warehouse is a Production server because it is highlighted in red in the sidebar, while oracle_morrihos_organize_hml is highlighted in green, as shown in the provided mockup.

Screenshots / Mockups

Issue Priority

Priority: 3

Issue Component

Component: Metadata

[mattcasters]

That would depend on the environment you're in, right, not the database connection itself.

[vitorsantos-commits]

I understand the Environment-driven approach, Matt, but I still believe having the option to set a color directly on the Database Connection is vital for user experience.

In many real-world scenarios, we have specific databases that are always production (like a legacy ERP or a sensitive DW) regardless of the Hop Environment we are using. If the color is tied only to the Environment, a user might still get confused if they have multiple connections open from different sources.

My proposal is to have a 'Display Color' field in the Connection Metadata. This would allow:

Visual Consistency: The user knows that 'Red' always means that specific sensitive database.

Immediate Identification: Even if I'm in a 'Dev' environment, if I'm pointing to a 'Production' database for a read-only task, I want to see it in red to be extremely careful.

DBeaver does this very well because it treats the connection's visual identity as a safety layer. Could we consider this as an optional field in the Connection Metadata?"

[mattcasters]

So yeah, that makes a lot of sense. So perhaps we can set the color to some RGB value ${HIGHLIGHT_COLOR}, in the advanced tab somewhere. That way you can define what that looks like in the envirnoment settings or manually. Something like #FF0000 for production and #000000 as the default.