task(deps): update go-scalingo to remove support for the db-api - #1248
task(deps): update go-scalingo to remove support for the db-api#1248matthieu526-scalingo wants to merge 2 commits into
Conversation
sc-david-voisin
left a comment
sc-david-voisin
left a comment
There was a problem hiding this comment.
SGTM, one question though
| Examples: []string{ | ||
| "scalingo database-firewall-managed-ranges my-db-id", | ||
| "scalingo --database my-db database-firewall-managed-ranges", | ||
| "scalingo database-firewall-managed-ranges", |
There was a problem hiding this comment.
praise: good catch, they are not linked to a database
| require ( | ||
| github.com/AlecAivazis/survey/v2 v2.3.7 | ||
| github.com/Scalingo/go-scalingo/v11 v11.1.1 | ||
| github.com/Scalingo/go-scalingo/v11 v11.1.2-0.20260810110303-774d8583f620 |
There was a problem hiding this comment.
question: the incoming go-scalingo CHANGELOG indicated "breaking change", so I suppose this version is not the definitive one ?
There was a problem hiding this comment.
Yes, that's exactly why I put Update go-scalingo to the new released version in the description 🙂
In any case I'll be waiting on UFS before going further.
There was a problem hiding this comment.
Ok, I misunderstood its meaning.
And if you wait for UFS, it is all good!
|
Closing this for now. The behaviour is not the one expected. The switch of endpoint comes with a side effect, where the "prefix" are different. IE |
2 participants
The DB API has been deprovisionned and is not required anymore.
This is pending confirmation from UFS here.
Based on this go-scalingo PR.
Fix #1247 .