-
Notifications
You must be signed in to change notification settings - Fork 137
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
fallback to json default cfg path if yaml does not exist #1810
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1810 +/- ##
==========================================
- Coverage 57.93% 50.19% -7.75%
==========================================
Files 50 70 +20
Lines 3119 4202 +1083
==========================================
+ Hits 1807 2109 +302
- Misses 1154 1858 +704
- Partials 158 235 +77 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Will need to rebase once #1814 merges. |
Needs a rebase. |
Signed-off-by: Janine Olear <[email protected]>
d218862
to
53fc3e7
Compare
Sry @haydentherapper, just saw this and rebased it now 👍 |
Signed-off-by: Janine Olear <[email protected]>
Closes #1811
Summary
The PR #1720 has changed the default config path from
/etc/fulcio-config/config.json
to/etc/fulcio-config/config.yaml
. This caused problems with non-explicitly configured environments.Release Note
Check and fallback to default JSON config if the default YAML configuration file did not exist.
Documentation