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

WordPress Developer's Guide Should Steer Users to Secrets Management #9200

Closed
joshkoenig opened this issue Sep 3, 2024 · 0 comments · Fixed by #9247
Closed

WordPress Developer's Guide Should Steer Users to Secrets Management #9200

joshkoenig opened this issue Sep 3, 2024 · 0 comments · Fixed by #9247
Assignees
@rachelwhitton
Labels
Topic: Secrets Topic: WordPress WordPress-specific Type: Fix Content Issue or PR to resolve incorrect information in the docs

Comments

@joshkoenig
Copy link
Member

Re: WordPress Developer's Guide

Priority: Medium

Issue Description:

This doc still recommends deprecated (Lockr) or less-secure (/files/private) pathways for managing secrets.

Suggested Resolution

Update to point all users to Pantheon Secrets Management
@stevector stevector added Topic: WordPress WordPress-specific Type: Fix Content Issue or PR to resolve incorrect information in the docs labels Sep 4, 2024
@rachelwhitton rachelwhitton mentioned this issue Oct 9, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rachelwhitton rachelwhitton

Labels
Topic: Secrets Topic: WordPress WordPress-specific Type: Fix Content Issue or PR to resolve incorrect information in the docs
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Recommend Pantheon Secrets instead of Lockr pantheon-systems/documentation
3 participants
@joshkoenig @stevector @rachelwhitton