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.

Sign up for GitHub

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

Jump to bottom

(docs) Update pdk_known_issues.md to add expired cert for v3.0.1 #1386

Merged
merged 2 commits into from
Aug 9, 2024
Merged

(docs) Update pdk_known_issues.md to add expired cert for v3.0.1 #1386

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e3e97af
Update pdk_known_issues.md to add expired cert for v3.0.1
pmcmaw Aug 9, 2024
02b427e
Update pdk_known_issues.md
pmcmaw Aug 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/pdk_known_issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,3 +7,7 @@ Upgrading the pdk from one version to another, e.g., going from `3.0.0.0` to `3.
For example, if you have customized the `cert.pem` to trust a self-hosted git repository server like `git.self.hosted`, then after the PDK upgrade an error may appear during PDK usage like `fatal: unable to access 'https://git.self.hosted/companyxyz/mymodule.git/': SSL certificate problem: self signed certificate`.

For more information on how to correct this known issue see the [PDK Troubleshooting](pdk_troubleshooting.md#pdk-failing-to-pull-from-custom-git-server) section.

## PDK v3.0.1 Cert expired

This issue was resolved and shipped in PDK v3.1.0, if you are seeing an issue in relation to an expired cert, please upgrade the PDK.
Loading