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

Registry server: should PATCHing artifacts merge YAML fields? #1222

Open
timburks opened this issue Sep 5, 2023 · 0 comments
Open

Registry server: should PATCHing artifacts merge YAML fields? #1222

timburks opened this issue Sep 5, 2023 · 0 comments

Comments

@timburks
Copy link
Contributor

timburks commented Sep 5, 2023

As a followup to #1221, it seems useful to support some form of merging at the API level. Currently the Registry API only supports ReplaceArtifact, which differs from other resource types, because early API reviewers felt that artifacts should be atomic resources. This was prior to the emergence of a preference for YAML-formatted artifacts, which could be fairly easily merged. Should we revisit this in the API, perhaps with content type-specific features? (Maybe we only merge YAML and JSON artifacts)

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

No branches or pull requests

1 participant