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

Fix typo in 'metadata' #128

Merged
merged 1 commit into from
Aug 9, 2024
Merged

Fix typo in 'metadata' #128

merged 1 commit into from
Aug 9, 2024

Conversation

negz
Copy link
Member

@negz negz commented Aug 8, 2024

Description of your changes

I noticed this typo in an error while experimenting with the function.

I have:

Signed-off-by: Nic Cope <[email protected]>
@@ -240,7 +240,7 @@ spec:
}
```

> Note that when returning multiple resources, we need to set different `metadata.name` or `matadata.annotations."krm.kcl.dev/composition-resource-name" ` to distinguish between different resources in the composition functions.
> Note that when returning multiple resources, we need to set different `metadata.name` or `metadata.annotations."krm.kcl.dev/composition-resource-name" ` to distinguish between different resources in the composition functions.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this really true?

At the Crossplane end, what matters is that the composition-resource-name is unique. It's fine for two different composed resources to have the same metadata.name, as long as they're of different types.

@Peefy
Copy link
Collaborator

Peefy commented Aug 9, 2024

Good Catch! LGTM!

If the user sets the same resource name, the implementation logic before is that function-kcl will overwrite/merge dup resources. After PR #126, it will check the uniqueness of the resource name at the function level.

@Peefy Peefy merged commit 704b929 into crossplane-contrib:main Aug 9, 2024
6 checks passed
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.

2 participants