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.

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

Closed
azdagron opened this issue Oct 26, 2022 · 4 comments · Fixed by #3808
Closed

Remove x509_svid_ttl column #3536

azdagron opened this issue Oct 26, 2022 · 4 comments · Fixed by #3808
Assignees
Labels
priority/urgent Issue is approved and is must be completed in the assigned milestone
Milestone

Comments

@azdagron
Copy link
Member

azdagron commented Oct 26, 2022

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.

@azdagron azdagron added the priority/urgent Issue is approved and is must be completed in the assigned milestone label Oct 26, 2022
@azdagron azdagron added this to the 1.6.0 milestone Oct 26, 2022
@dennisgove
Copy link
Contributor

I'm happy to take this on.

@azdagron
Copy link
Member Author

That'd be great! Thanks @dennisgove. The main branch will open up for 1.6.0 changes roughly after we ship 1.5.2 in a few months. I'll assign this to you.

@azdagron
Copy link
Member Author

@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.

@dennisgove
Copy link
Contributor

Yup, happy to work on it. I'll try to get a PR in in the next week.

dennisgove added a commit to dennisgove/spire that referenced this issue Jan 27, 2023
Fixes spiffe#3536

Signed-off-by: Dennis Gove <dgove1@bloomberg.net>
dennisgove added a commit to dennisgove/spire that referenced this issue Jan 27, 2023
Fixes spiffe#3536

Signed-off-by: Dennis Gove <dgove1@bloomberg.net>
azdagron pushed a commit that referenced this issue Jan 29, 2023
Fixes #3536

Signed-off-by: Dennis Gove <dgove1@bloomberg.net>
stevend-uber pushed a commit to stevend-uber/spire that referenced this issue Oct 16, 2023
Fixes spiffe#3536

Signed-off-by: Dennis Gove <dgove1@bloomberg.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/urgent Issue is approved and is must be completed in the assigned milestone
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants