-
Notifications
You must be signed in to change notification settings - Fork 75
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
Bug: Outdated references to ua #2849
Comments
The security-status one is, unfortunately, there forever 😨 No, I mean, we must keep JSON keys to assure compatibility, and this response specifically is not versioned :/ |
Perfect - thanks for the insight :) Do we need to take any action on the collect logs one, or is that also part of the API plan? |
nono collect logs can and should be changed |
Fixed in #2928 |
Description of the bug
Not a bug exactly, but during my survey of the docs I discovered some places that still refer to
ua
in the code that we should look to update topro
if possible:ua_logs.tar.gz
If these can be updated, we will also need to update the corresponding docs pages:
howtoguides/how_to_collect_logs
Edit: The following do not need to be actioned currently, as per discussion below
ua
for the status of the pro client on theexplanations/how_to_interpret_the_security_status_command
pageThe text was updated successfully, but these errors were encountered: