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

params: support for tracking all params in a file #3431

Merged
merged 7 commits into from
May 21, 2022

Conversation

skshetry
Copy link
Member

@skshetry skshetry commented Apr 8, 2022

@jorgeorpinel
Copy link
Contributor

jorgeorpinel commented Apr 12, 2022

Is there a syntax for run/ stage add -p to indicate all params in the default params file? What about in a custom params file? If so those refs would need an update probably. Thanks. (See also iterative/dvc#4112 (comment).)

@jorgeorpinel

This comment was marked as outdated.

@jorgeorpinel jorgeorpinel changed the title document about support for tracking all parameters in a given file params: support for tracking all params in a file Apr 29, 2022
Comment on lines 54 to 61
dependency. They consist of a list of params to track in one of these formats:

1. A param key/value pair that can be found in `params.yaml` (default
params file);
2. A dictionary named by the file path to a custom params file, and with a
list of param key/value pairs to find in it;
3. An empty set (give no value or use `null`) named by the file path to a
params file: to track all the params in it dynamically.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The detail given now may be too much but we can address that... (from #3431 (review))

Well... I ended up adding even more details here. This should at some point get extracted to a separate guide (#2572) but OK to keep for now, I think.

@gatsby-cloud
Copy link

gatsby-cloud bot commented Apr 29, 2022

Gatsby Cloud Build Report

dvc.org

🎉 Your build was successful! See the Deploy preview here.

Build Details

View the build logs here.

🕐 Build time: 56s

Performance

Lighthouse report

Metric Score
Performance 🔶 63
Accessibility 💚 98
Best Practices 🔶 83
SEO 💚 93

🔗 View full report

@jorgeorpinel jorgeorpinel self-assigned this Apr 30, 2022
@jorgeorpinel jorgeorpinel requested a review from dberenbaum April 30, 2022 02:26
@jorgeorpinel

This comment was marked as resolved.

@jorgeorpinel

This comment was marked as resolved.

@jorgeorpinel
Copy link
Contributor

@skshetry PTAL

@jorgeorpinel jorgeorpinel requested a review from daavoo May 11, 2022 16:00
@shcheklein
Copy link
Member

@skshetry @jorgeorpinel merging this?

@jorgeorpinel
Copy link
Contributor

jorgeorpinel commented May 21, 2022

merging this?

Yeah I was expecting approval from @skshetry since I took this over but haven't heard back. There's approval anyway (thanks @daavoo) so lets merge 🚀

@jorgeorpinel jorgeorpinel merged commit 26fffa1 into master May 21, 2022
@jorgeorpinel jorgeorpinel deleted the document-params-full-tracking branch May 21, 2022 03:35
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

Successfully merging this pull request may close these issues.

5 participants