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

provider/postgis: Clean out deprecated connection params #979

Closed
2 tasks
ARolek opened this issue Feb 27, 2024 · 7 comments · Fixed by #986
Closed
2 tasks

provider/postgis: Clean out deprecated connection params #979

ARolek opened this issue Feb 27, 2024 · 7 comments · Fixed by #986

Comments

@ARolek
Copy link
Member

ARolek commented Feb 27, 2024

In v0.15.0 support for a connection string uri was added to provider/postgis. When this change was made, we marked the old connection params as deprecated. These params now need to be removed. This issue is for tracking this removal from the following places:

  • provider/postgis: This package needs to remove support for the old connection params. The README should also be updated.
  • .github/: The CI uses the old connection params in a few places and needs to be migrated.
@iwpnd
Copy link
Member

iwpnd commented Feb 28, 2024

I can take it. Do you think it makes sense to create Github project to collect open work like this? Have to admit I completely forgot about it - and actually volunteered for it back then. 😞

@ARolek
Copy link
Member Author

ARolek commented Feb 28, 2024

I can take it.

That would be awesome! Your recent PR made me realize this hasn't been done but should absolutely be cleaned up. I'm on a "purge all the unnecessary things" kick right now 😉

Do you think it makes sense to create Github project to collect open work like this

I would absolutely be in favor of this. We could then organize issues based on priority if contributors are looking to pick up an issue. I can spin up a project called "Roadmap" and we can start adding issues to it. How does that sound?

@iwpnd
Copy link
Member

iwpnd commented Feb 28, 2024

Great 👌🏻 let’s do that

@ARolek
Copy link
Member Author

ARolek commented Feb 28, 2024

@iwpnd done. I also invited you to it so you can help groom the backlog ;-)

@ARolek
Copy link
Member Author

ARolek commented Mar 18, 2024

@iwpnd have you had a chance to look at this issue? I'm hoping to include these changes in the upcoming release. The upcoming release has a lot of vuln squashing in it, so I would like to get a version cut in the not too distant future. LMK if you want to tag team this one.

@iwpnd
Copy link
Member

iwpnd commented Mar 18, 2024

Gosh 19d ago already. I'm swamped at work right now and happy to not touch the keyboard in the evening. But I do have a three hour train ride on Wednesday reserved for it. ☝🏻🤞🏻

@ARolek
Copy link
Member Author

ARolek commented Mar 18, 2024

@iwpnd No worries!!

I'm swamped at work right now and happy to not touch the keyboard in the evening.

I can relate. A lot to juggle right now. No pressure.

But I do have a three hour train ride on Wednesday reserved for it.

Excellent. Feel free to push up a branch if you need some help along the way. Thanks for tackling this one!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants