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

Tag 'latest-alpine', 'latest-buster', '1', '2', '2-alpine', '2.3-alpine', '2-buster', '2.3-buster' images #1820

Closed
ryboe opened this issue May 31, 2023 · 4 comments
Closed

Tag 'latest-alpine', 'latest-buster', '1', '2', '2-alpine', '2.3-alpine', '2-buster', '2.3-buster' images #1820

ryboe opened this issue May 31, 2023 · 4 comments
Assignees
@jackwotherspoon
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@ryboe
Copy link

ryboe commented May 31, 2023 •
edited
Loading

Feature Description

I'm using the alpine version of cloud-sql-proxy. I would like to always pull the latest v2 version of the container, but there's no way to do that. Adding these tags would make it easier for users to decide how to weigh the risk of updating vs. the risk of falling behind:

1
1.33
2
2.3
2-alpine
2.3-alpine
2-buster
2.3-buster
latest-alpine
latest-buster
@ryboe ryboe added the type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. label May 31, 2023
@enocom enocom added the priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. label Jun 1, 2023
@enocom
Copy link
Member

enocom commented Jun 1, 2023

Thanks for the suggestion @ryboe. I think it's a reasonable proposal and we'll work it into our upcoming backlog.

@ryboe ryboe mentioned this issue Jun 1, 2023
Closed
@enocom
Copy link
Member

enocom commented Jul 19, 2023

Sorry we've let this slip through the cracks. I'll make sure we have it for the next release.

@enocom enocom assigned jackwotherspoon and unassigned enocom Jul 31, 2023
This was referenced Aug 15, 2023
Merged
Merged
@enocom
Copy link
Member

enocom commented Aug 16, 2023

This is done. Thanks @jackwotherspoon for getting this over the line.

@enocom
Copy link
Member

enocom commented Aug 16, 2023

image

@enocom enocom closed this as completed Aug 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jackwotherspoon jackwotherspoon

Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@enocom @ryboe @jackwotherspoon