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.

Sign up for GitHub

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

Jump to bottom

Registry tool: should registry apply merge fields? #1221

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

Registry tool: should registry apply merge fields? #1221

timburks opened this issue Sep 5, 2023 · 0 comments

Comments

@timburks
Copy link
Contributor

timburks commented Sep 5, 2023

A user suggested that it would be helpful if registry apply could merge values in artifacts. For example, after the following two files were applied, there would be a single artifact with both team and email fields set. Currently each apply fully replaces an existing artifact.

apiVersion: apigeeregistry/v1
kind: FieldSet
metadata:
  parent: apis/sample
  name: support
data:
  definitionName: projects/PROJECTID/locations/global/artifacts/support
  values:
    team: "Team"

apiVersion: apigeeregistry/v1
kind: FieldSet
metadata:
  parent: apis/sample
  name: support
data:
  definitionName: projects/PROJECTID/locations/global/artifacts/support
  values:
    email: "[email protected]"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Apigee API Registry
Status: Inbox
Milestone
No milestone
Development

No branches or pull requests
1 participant
@timburks