Forum Discussion
CirrusChanges to DO and AS3 GitHub - no longer monitored
I see Changes to DO and AS3 GitHub pages have been updated with these notices:
"
AS OF FEBRUARY 2026, THIS GITHUB REPOSITORY WILL NO LONGER BE MONITORED OR UPDATED.
This repository will remain available, at least temporarily. You can find the latest RPMs and other files on MyF5 Downloads. Refer to 'Filing Issues and Getting Help' for additional details.
"
I'm also seeing [Deprecated] notices on some VS Code extensions, which may or may not be related.
I haven't been able to find any larger announcements regarding these.
I have not been able to find any additional detail.
Does anyone know if we are about to see a a large shift (or loss) of tooling around BIG-IP?
8 Replies
zdenekzembaAltostratus
Noticed that as well, lets see whether we get some more info... Thx for pointing this out
kuhlenkampNimbostratus
I agree. What is going on here?
Should we stop using DO & AS3 in favor of something else?
Please provide guidance.- MJ_1024
I'm in no direct position to provide guidance (no secret insight here), but from what I hear and suspect is this likely is more of a sign of added maturity (bringing AS3 , DO, and others closer) than anything else. Probably some 'benefits' of being more in-house in the development pipeline and having more 'formal' releases rather than what we have had in the past.
If so, hopefully this ends up overall good for these APIs/Tooling longevity, even if some processes might have to change in the short term. I will miss the easy access to create GitHub tickets / search through old issues (I personally always found that easier than trying to search through bug reports / active tickets for something else like bigip).
Still, I look forward to a more formal public update/announcement from F5 regarding this to better plan for the future.
- Juergen_Mang
MVP
I do not like this change. My current pipelines are downloading the RPM's from GitHub. With the move to myF5 Downloads that would not be possible anymore.
I vote for a possibility to download files from myF5 without going through the current login process. This would be also great for other files like Attack Signatures.
- kuhlenkamp
yes, need a bot ID or something that can download from F5. I don't know if that is possible currently....
juanboticari0Apparently they will be introducing a new declarative API in BIG-IP 21.1.
Source: https://www.f5.com/es_es/company/blog/a-sneak-peek-into-f5-big-ip-v21-1-ai-security-pqc-and-software-enhancements
carlbidwell268Yeah, you’re not the only one reading into this; it does feel like a quiet shift rather than a clearly announced change. From what’s visible, AS3 and DO have already been moving toward a more “maintenance/LTS” style lifecycle for a while, with fewer feature updates and more compatibility-focused releases . So the GitHub “no longer monitored” notice seems less like a sudden kill switch and more like F5 formalizing what was already happening behind the scenes.
I wouldn’t expect an immediate break in existing setups; these tools are still widely used and should continue working; but it’s a pretty strong signal to start planning around newer approaches (Central Manager, BIG-IP Next, or API-driven automation). The lack of a big announcement is frustrating, but historically F5 has been shifting direction gradually rather than making hard deprecation calls upfront. Here is another discussion where you can add value:
https://community.f5.com/discussions/technicalforum/f5-big-ip-source-dnsaudit-logs-%E2%80%94-structured-format-for-siem-ingestion/346115
