Have CLI place generated YAML file into the perses calculation directory
See original GitHub issueCurrently, the CLI generates a YAML file with the updated overridden fields, but it places it into a file like
parsed-2022-04-18-20:51:55-my.yaml
rather than actually putting it in the perses calculation output directory where it would be useful.
We should fix this so that we can pull useful information from it, like what calculation was actually performed to generate all the files in this directory.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Import and export YAML configuration using CLI
Learn how to use the YAML configuration CLI to import and export YAML configuration. A YAML configuration fragment is created by exporting from...
Read more >How to dynamically handle UNIX/Windows directory ...
We facing a problem where we need to configure a path in one of our config-file.yml . It's a path to an CLI-Script....
Read more >YAML Path and Command-Line Tools - GitHub
This project presents and utilizes YAML Paths, which are a powerful, intuitive means of identifying one or more nodes within YAML, EYAML, or...
Read more >How to Create Yaml File - Code Beautify
Creating an YAML file requires a basic understanding of YAML and why it's used as configuration files in Kubernetes, Ansible, CircleCI etc.
Read more >Work with the YAML format for Release
Here are a few simple XL CLI command line examples to generate YAML files from your existing configurations. Generate a YAML file for...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Oh my bad, the tab didn’t update itself and I missed @mikemhenry comment. Sorry! Will reopen.
No worries, when I saw it was closed I thought “wow I can’t believe Iván got those two things done already”