Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Remove deprecated https://meltano.com/discovery.yml
See original GitHub issueMigrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3240
Originally created by @pandemicsyn on 2022-02-11 18:40:03
Quoting @aaronsteers from https://gitlab.com/meltano/meltano/-/merge_requests/2525#note_840195158:
Perhaps we should push a (fake) version bump there so users are still directed that their
discovery.ymlis out of date and that they should upgrade?
I think it’s worth opening a ticket for removing the deprecated discovery.yml from meltano.com - just so we don’t lose visibility to that. Do you mind logging that for our follow-up?
Pushing a fake version bump or waiting for something like #2299 to land (which will trigger a legit bump) seem’s like a good tactic to cut down on the number of users using an older version. I’m not sure at what point we’d want to remove the old discovery.yml but we can probably keep an eye on our request log for the marketing site and wait for traffic to die down to a level low enough that we feel comfortable removing it.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@DouweM @aaronsteers It sounds like it’s ideal for this file to stay a little while longer for folks who are using older versions. Maybe we should revisit removing this EOY instead?
@aaronsteers Wouldn’t this break old Meltano versions? Or I guess they’d fall back on their cached/bundled copy.
I don’t think we need this today, no.