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

[v0.5] ensure valid release name for agent #1356

Merged
merged 5 commits into from
Mar 2, 2023

Conversation

manno
Copy link
Member

@manno manno commented Mar 1, 2023

Backport of #1353

Refers to rancher/rancher#40684

Mario Manno added 3 commits March 1, 2023 13:40
Bundles that were created directly could still have an invalid bundle
name.
Directly created bundles should use the same sanitization as bundles
created via `fleet apply`.

We still don't allow '.', because it's not DNS label safe.
@manno
Copy link
Member Author

manno commented Mar 1, 2023

I have trouble testing this locally. This is not ready yet.

Mario Manno added 2 commits March 2, 2023 12:01
Adding the token prefix to the cluster name could exceed 63 characters
and the ClusterRegistrationToken would not have been created. The error
was silently dropped.
`^1.19` is equivalent to `>=1.19.0 <2.0.0`, depending on the github
runner's cache, we might get a new version than expected.

See: https://github.com/npm/node-semver#ranges
@manno manno marked this pull request as ready for review March 2, 2023 12:39
@manno manno requested a review from a team as a code owner March 2, 2023 12:39
@manno manno merged commit b90a1d3 into release/v0.5 Mar 2, 2023
@manno manno deleted the v0.5/ensure-valid-release-name-for-agent branch March 2, 2023 14:35
@kkaempf
Copy link
Collaborator

kkaempf commented Mar 6, 2023

rancher/rancher#40684 got closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants