chore: Added docs section on env vars in yaml#2792
chore: Added docs section on env vars in yaml#2792feast-ci-bot merged 3 commits intofeast-dev:masterfrom
Conversation
|
I just noticed a previous commit (that I thought was already merged) has found its way into this PR. Please let me know if I should create a new PR with only the latest commit. Thanks. |
Codecov Report
@@ Coverage Diff @@
## master #2792 +/- ##
==========================================
- Coverage 80.59% 80.44% -0.15%
==========================================
Files 173 173
Lines 15006 15254 +248
==========================================
+ Hits 12094 12271 +177
- Misses 2912 2983 +71
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
|
Thanks for the contribution @creativedutchmen ! I think the previous commit is okay to pull in since there's no merge conflicts. |
|
/ok-to-test |
|
Actually @creativedutchmen you'll need to signoff your commit - you should be able to follow the instructions at https://github.com/feast-dev/feast/pull/2792/checks?check_run_id=6883873559 |
Signed-off-by: Huib Keemink <huib.keemink@jedlix.com>
Signed-off-by: Huib Keemink <huib.keemink@jedlix.com>
3c9bfef to
2ba4e2e
Compare
|
I just learned it's possible to set a default like |
Signed-off-by: Huib Keemink <huib.keemink@jedlix.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: achals, creativedutchmen The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Because it was unclear to me you could do this, and there was another question in Slack, I've added a section to the docs to explain you can do this: