Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Properly save runner name in GCP metadata #21

Merged
merged 1 commit into from
Jun 14, 2024

Conversation

gabriel-samfira
Copy link
Member

GARM expects providers to return the runner name and the provider ID of the runner once it's done creating the instance. The GCP provider was mutating the name and converting it to lowercase.

In GCP, the instance name is the ID of the VM and GCP has the requirement that only lowercase letters can be used for instance names.

In GARM, the runner name is the ID, and GARM uses both lower and upper case letters for the name.

The GCP provider was mutating the name and converting it to lowercase. When GARM listed all runners from the provider and cross checked the name to be the same, the check was failing due to the fact that GARM is case sensitive and expected the name to be identical.

This change saves the original name in the metadata of the VM. Labels seem to have the same requirements as the instance name for both keys and values.

GARM expects providers to return the runner name and the provider ID
of the runner once it's done creating the instance. The GCP provider was
mutating the name and converting it to lowercase.

In GCP, the instance name is the ID of the VM and GCP has the requirement
that only lowercase letters can be used for instance names.

In GARM, the runner name is the ID, and GARM uses both lower and upper case
letters for the name.

The GCP provider was mutating the name and converting it to lowercase. When
GARM listed all runners from the provider and cross checked the name to be
the same, the check was failing due to the fact that GARM is case sensitive
and expected the name to be identical.

This change saves the original name in the metadata of the VM. Labels seem
to have the same requirements as the instance name for both keys and values.

Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
@gabriel-samfira gabriel-samfira merged commit 494d2ef into cloudbase:main Jun 14, 2024
1 check passed
@gabriel-samfira gabriel-samfira deleted the fix-instance-name branch June 14, 2024 18:18
@fabi200123 fabi200123 mentioned this pull request Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant