Skip to content

The Gitpod Installer randomises ordering of environment variables for components #11000

@mads-hartmann

Description

@mads-hartmann

Bug description

I think we have a regression in the Installer that makes the environment variables order for components random (PR). By converting the env vars to a map and then back to a slice I believe we will randomise ordering as the map doesn't maintain any kind of stable ordering. This causes drift in ArgoCD similar to the issue we had with ports previously (PR)

Steps to reproduce

We're seeing this in or SaaS deployments that are managed by ArgoCD.

Workspace affected

No response

Expected behavior

The YAML produced by the Installer should be the same given the same configuration.

Example repository

No response

Anything else?

No response

Metadata

Metadata

Assignees

Labels

type: bugSomething isn't working

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions