fix(manager/fleet): Make name optional for target customizations in FleetFile schema#36085
Merged
rarkins merged 7 commits intorenovatebot:mainfrom May 24, 2025
Merged
Conversation
|
|
rarkins
suggested changes
May 22, 2025
Co-authored-by: Rhys Arkins <rhys@arkins.net>
viceice
reviewed
May 22, 2025
rarkins
approved these changes
May 23, 2025
|
🎉 This PR is included in version 40.27.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
viceice
approved these changes
May 26, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Target customizations for fleet do not actually need a name (see https://fleet.rancher.io/ref-fleet-yaml). This PR makes the name in the schema optional and generates a dependency name if none is provided by the
fleet.yaml.Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: