Skip to content

Team Security Tracking: RFC249 Secret Management Tracking

Created by: chayim

Plan

Required work for RFC 249. Nice to have work that's relevant to this work tracked in #15475 https://docs.google.com/document/d/1HzO7szEm-h4fqlQOnVbcJdpDmfQiM7Rb-Tz4CMEYl-Q/edit?usp=sharing

Main work sequence order of operations #17793 (closed) -> #17797 (closed) -> #17801 (closed) -> #17802 (closed) -> #17803 (closed) -> #17804 (closed) -> [#17806 (closed), #17807 (closed)] -> #17808 (closed) -> #17809 (closed) -> [#17810 (closed), #17811 (closed)] -> #17812 (closed) -> #17813 (closed) -> #17814 -> #17815

How to do secrets

Availability

If you have planned unavailability this iteration (e.g., vacation), you can note that here.

Tracked issues

@unassigned

Completed

@ElizabethStirling: 1.50d

Completed: 1.50d

Legend

  • 👩 Customer issue
  • 🐛 Bug
  • 🧶 Technical debt
  • 🎩 Quality of life
  • 🛠️ Roadmap
  • 🕵️ Spike
  • 🔒 Security issue
  • :shipit: Pull Request