Add link to advanced runtime_params configuration

DimedS commented 4 days ago

Description

Closes #3562

Developer Certificate of Origin

We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a Signed-off-by line in the commit message. See our wiki for guidance.

If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.

Checklist

[ ] Read the contributing guidelines
[ ] Signed off each commit with a Developer Certificate of Origin (DCO)
[ ] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Updated the documentation to reflect the code changes
[ ] Added a description of this change in the RELEASE.md file
[ ] Added tests to cover my changes
[ ] Checked if this change will affect Kedro-Viz, and if so, communicated that with the Viz team

ankatiyar commented 4 days ago

I'm wondering if we should update the above "How to specify parameters at runtime" section to use the runtime_params: resolver primarily and then mention that one can directly overwrite params too but it isn't recommended?

DimedS commented 3 days ago

I'm wondering if we should update the above "How to specify parameters at runtime" section to use the runtime_params: resolver primarily and then mention that one can directly overwrite params too but it isn't recommended?

Do you mean we should merge the two articles into the first one and remove the advanced article?

ankatiyar commented 2 days ago

Do you mean we should merge the two articles into the first one and remove the advanced article?

I mean, keep the section in Advanced Configuration as it is but also mention the runtime_params: here in this section. Would like to see what others think.

kedro-org / kedro