Skip to content

Implementing on env egress schema #430

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
Open
wants to merge 1 commit into
base: staging
Choose a base branch
from
Open

Implementing on env egress schema #430

wants to merge 1 commit into from

Conversation

aryanjassal
Copy link
Member

@aryanjassal aryanjassal commented Jun 24, 2025 •
edited
Loading

Description

A schema will dictate which secrets need to be exported and which ones aren't, better enforcing POLP, and make secrets management easier.

Issues Fixed

Tasks

  • 1. Use ajv to validate a schema
  • 2. Use the schema to export a set of secrets
  • 3. Incorporate fail-fast pattern on error
  • 4. Add schema composition

Final checklist

  • Domain specific tests
  • Full tests
  • Updated inline-comment documentation
  • Lint fixed
  • Squash and rebased
  • Sanity check the final build

@aryanjassal aryanjassal self-assigned this Jun 24, 2025
@linear Linear
Copy link

linear bot commented Jun 24, 2025

ENG-638

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@aryanjassal aryanjassal

Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Add egress schema to polykey secrets env
1 participant
@aryanjassal