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

SA: allow a profile name to be stored alongside an authz #7955

Closed
Tracked by #7309
aarongable opened this issue Jan 17, 2025 · 0 comments · Fixed by #7956
Closed
Tracked by #7309

SA: allow a profile name to be stored alongside an authz #7955

aarongable opened this issue Jan 17, 2025 · 0 comments · Fixed by #7956
Assignees
@aarongable
Milestone
Sprint 2025-01-21

Comments

@aarongable
Copy link
Contributor

No description provided.

This was referenced Jan 17, 2025
Open
Merged
Merged
@aarongable aarongable self-assigned this Jan 17, 2025
@aarongable aarongable added this to the Sprint 2025-01-14 milestone Jan 17, 2025
aarongable added a commit that referenced this issue Jan 21, 2025
@aarongable
Add schema for profile column in authz2 table (#7954)
1806294 
Use MariaDB's "instant add column" feature to add a new
certificateProfileName column to the existing authz2 table. This column
is nullable to reflect the fact that profiles are optional, and to
mirror the similarly-added column on the orders table.

This change is standalone, with no code reading or writing this field,
so that it can be deployed to production and a follow-up change can
begin reading and writing the field all at once with no deployability
concerns.

Part of #7955
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aarongable aarongable

Labels
None yet
Projects
None yet
Milestone
Sprint 2025-01-21
Development

Successfully merging a pull request may close this issue.

SA: Support profiles associated with authorizations letsencrypt/boulder
1 participant
@aarongable