Add JSON and TOML support to init and rotate-token commands
#32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Structured output simplifies automation tasks that rely on having Fermyon Cloud GPU proxy deployed Signed-off-by: Thorsten Hans <[email protected]>
ThorstenHans
force-pushed
the
feat/formatted-output
branch
from
c7765b6
to
e0beefd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Although the configuration snippet is printed as TOML to
stdout, it's embedded in log messages and usage instructions.This is great for new users, and still the default behavior when running either
spin cloud-gpu initorspin cloud-gpu rotate-token.However, having the output in structured format (either
JSONorTOML) simplifies automation tasks.With this PR users can provide either the
--tomlor--jsonflag to both commands.Other log messages were moved to
stderr