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-experimental: "decode" command for decoding known experimental protobuf types #102

Open
timburks opened this issue Sep 15, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@timburks
Copy link
Contributor

timburks commented Sep 15, 2022

registry-experimental decode TYPE would read binary data from standard input and attempt to unmarshal it as an encoded proto of the specified type, and then write the result as JSON (by default) or YAML. TYPE could be a fully-resolved type or, when unambiguous, a known message name. For example, the following invocations might get and decode messages of type google.cloud.apigeeregistry.applications.v1alpha1.Index:

registry get artifacts/index --raw | registry-experimental decode google.cloud.apigeeregistry.applications.v1alpha1.Index

registry get artifacts/index --raw | registry-experimental decode Index

This would allow us to move all of the v1alpha1 protos out of the main registry repo and into this one.

registry-experimental decode --list-types might be useful for printing a list of known types.

@timburks timburks added the enhancement New feature or request label Sep 15, 2022
@timburks timburks moved this to Todo in Apigee API Registry Apr 5, 2023
@timburks timburks moved this from Todo to Backlog in Apigee API Registry Apr 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant