You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a profile field to the SA's NewOrder request object.
Decide where to store it: a new column in the orders table? a new table?
Add a profile field to the SA's GetOrder response object.
We've decided to store nothing in the case that the client does not explicitly request a profile, so the default can be selected at finalize time.
The text was updated successfully, but these errors were encountered:
Adds `certificateProfileName` to the `orders` database table. The
[maximum
length](https://github.com/letsencrypt/boulder/pull/7325/files#diff-a64a0af7cbf484da8e6d08d3eefdeef9314c5d9888233f0adcecd21b800102acR35)
of a profile name matches the `//issuance` package.
Adds a `MultipleCertificateProfiles` feature flag that, when enabled,
will store the certificate profile name from a `NewOrderRequest`. The
certificate profile name is allowed to be empty and the database will
treat that row as [NULL](https://mariadb.com/kb/en/null-values/). When
the SA retrieves this potentially NULL row, it will be cast as the
golang string zero value `""`.
SRE ticket IN-10145 has been filed to perform the database migration and
enable the new feature flag. The migration must be performed before
enabling the feature flag.
Part of #7324
Add a profile field to the SA's NewOrder request object.
Decide where to store it: a new column in the orders table? a new table?
Add a profile field to the SA's GetOrder response object.
We've decided to store nothing in the case that the client does not explicitly request a profile, so the default can be selected at finalize time.
The text was updated successfully, but these errors were encountered: