-
Notifications
You must be signed in to change notification settings - Fork 486
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.
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
Remove x509_svid_ttl column #3536
Comments
I'm happy to take this on. |
That'd be great! Thanks @dennisgove. The |
@dennisgove is this something you are still willing to take? If so, repo is open now for 1.6.0 changes :) If not, no worries, one of the maintainers can also pick it up. |
Yup, happy to work on it. I'll try to get a PR in in the next week. |
Fixes spiffe#3536 Signed-off-by: Dennis Gove <dgove1@bloomberg.net>
Fixes spiffe#3536 Signed-off-by: Dennis Gove <dgove1@bloomberg.net>
Fixes #3536 Signed-off-by: Dennis Gove <dgove1@bloomberg.net>
Fixes spiffe#3536 Signed-off-by: Dennis Gove <dgove1@bloomberg.net>
In anticipation of introducing seperate X509-SVID and JWT-SVID TTL registration entry fields, two new columns were added to the registration entry model in the datastore (see #3174). Support was added to SPIRE core to support these fields in (#3445), which would consume these columns. However, while developing and evaluating the new support we came to the conclusion that backcompat and downgrade support became much simpler if the existing ttl column was used as it has traditionally been used, for the X509-SVID ttl.
As such, the x509_svid_ttl column added in #3174 is no longer relevant. In accordance with our deprecation policies, it can be removed in 1.6.0.
The field for the model was removed in 1.5.0 (see #3541) so that we could support a 1.6.0 --> 1.5.x downgrade. This means that new deployments of 1.5.x will NOT have the column. This means that the migration code MUST be idempotent, checking for existence of the column before trying to remove it.
The text was updated successfully, but these errors were encountered: