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

[feat] devOps friendly output format (JSON, YAML) #945

Open
vicary opened this issue May 9, 2021 · 6 comments
Open

[feat] devOps friendly output format (JSON, YAML) #945

vicary opened this issue May 9, 2021 · 6 comments

Comments

@vicary
Copy link

vicary commented May 9, 2021

Description

It should be a common use case to integrate Serverless Component into CI/CD pipelines, where outputs are usually parsed with scripts to further trigger other pipelines.

It would be really helpful if serverless deploy and serverless info allows an option for output formats, such as serverless deploy --format json.

This option should implies skipping the deploying TUI progress bar, which also solves #834.

@nabi-chan
Copy link

Hello, I am writing PR based on your Issue.
What information should be printed out to be of great help?

@vicary
Copy link
Author

vicary commented Jul 19, 2021

Thanks for making an effort. So in theory devOps pipelines should be programmatically friendly to parse, in general it should

  1. Remove CLI progress bar
  2. Show deployment outputs in JSON format, I am expecting the same data that can be referenced via the syntax ${output:...} in other components.

@nabi-chan
Copy link

Aha. So you want information like 'serverless info --debug' to be displayed in JSON or YAML format after the distribution pipeline is terminated?

@vicary
Copy link
Author

vicary commented Jul 21, 2021

Yes. Such that I can easily plug my own scripts to grep necessary information into our own CI/CD pipelines. For example I can send the ARN downstream to another repo that updates our k8s proxy.

@nabi-chan
Copy link

Thanks for your help!
Your answer is more help to this PR!

@vicary
Copy link
Author

vicary commented Jul 21, 2021

Glad to be of help!

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

No branches or pull requests

2 participants