Release 29 #2677
Merged
Release 29 #2677
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lucasmoura
force-pushed
the
release-29
branch
2 times, most recently
from
04e7b34
to
41fa8e9
Compare
|
@renanrodrigo updated |
renanrodrigo
approved these changes
Aug 1, 2023
lucasmoura
commented
Aug 1, 2023
debian/changelog
Outdated
| higher priority (GH: #2580) | ||
| - fix: ignore non-USN items on related usns | ||
| - landscape: add support for the service | ||
| - logging: update logger names |
There was a problem hiding this comment.
logging: update to ubuntupro logging namespace
lucasmoura
commented
Aug 1, 2023
debian/changelog
Outdated
| + send activityInfo after cli attach, enable and disable | ||
| + start recording when the machine has attached to a Pro subsctiption | ||
| - esm: create static files to pin packages from esm-infra and esm-apps with | ||
| higher priority (GH: #2580) |
There was a problem hiding this comment.
Double check indentation
lucasmoura
commented
Aug 1, 2023
lucasmoura
force-pushed
the
release-29
branch
4 times, most recently
from
51ac666
to
e123d07
Compare
If we detect we have a corrupted lock in the system, we are now alerting the user about that with steps to solve that scenario LP: #1996931
If we have not set the ssh keys when running integration tests, we might accidentally delete the ssh keys stored in the user .ssh folder. We are checking to see if the keys are stored in that folder before deleting it
Signed-off-by: Renan Rodrigo <[email protected]>
Signed-off-by: Renan Rodrigo <[email protected]>
lunar is now tested where kinetic is tested, except on some cases where it is not possible yet - those will be done in 3 months lunar is now part of the GH CI Signed-off-by: Renan Rodrigo <[email protected]>
When we are gathering related USNs, we must ensure that they are indeed USNs. To do that, we are ignoring any security id that doesn't start with USN
The previous interface to readurl had different return types depending on the request, and it propogated exceptions that were raised from the urllib library. Those urllib exceptions were then caught and used in various places throughout the codebase. The upcoming tls-in-tls implementation will require swapping out the urllib request function for a pycurl-based one, which will not have any of the same return types or exceptions as urllib, so we need to stop using urllib-specific things everywhere. To achieve this, I've defined a simple HTTPResponse tuple that will always be returned by the readurl function - this should be easily implemented by any underlying http implementation. Notice that the function always returns this tuple, even if there is a http code above 300. Previously we expected/excepted errors on 4xx/5xx responses, so I've changed a lot of the calling code to check the return code rather than except errors. The only error that is raised is now our exceptions.UrlError and I've redefined it to only be raised if something about the connection fails.
Same keys, just different names to standardize them all as pro. Fixes: #1539 Signed-off-by: Renan Rodrigo <[email protected]>
Signed-off-by: Renan Rodrigo <[email protected]>
Signed-off-by: Renan Rodrigo <[email protected]>
Fixes: #2463 Signed-off-by: Renan Rodrigo <[email protected]>
Always require a contract token in the environment if the test has an attachment step. If the whole feature requires attachment, require it on feature level. If the feature does not imply attachment, require it on scenario level. Signed-off-by: Renan Rodrigo <[email protected]>
This avoids a possible inconsistent state between checking if a file exists and trying to remove it. LP: #2025731 Signed-off-by: Renan Rodrigo <[email protected]>
Add JSON schema checks for both USN and CVE endpoints of the fix plan API
This way users who enabled esm will not risk getting automatic updates for packages if those don't come from the esm repositories, guaranteeing security patches will not be accidentally removed. Fixes: #2580 Signed-off-by: Renan Rodrigo <[email protected]>
…y to parse empty string
The API reference document showed both Python and CLI code to the user at the same time. Now through the use of tabs, the user can choose whether to view Python or the CLI version. Tabs are synced so their choice is applied to all entries. The API page is now made cleaner and more functional. This also converts the source doc from md to rst
* Docs front page overhaul - Revamp docs front page giving context for Pro services - Add tabs to separate services by user pathways - Add links to some relevant pages in our own docs - Add new explanation page on ESM services (from FAQ) - Change LHS nav menu to collapse some how-tos - Expand "how to enable esm-infra" to include esm-apps - Also added content on how to disable these
Define an incompatibility matrix for the services and reference it on each how-to-guide that shows how to enable a service that is incompatible with another service. Fixes: #2595
Signed-off-by: Renan Rodrigo <[email protected]>
Signed-off-by: Renan Rodrigo <[email protected]>
Helps maintain the user's system sbuild config
We used to have 28 as the devel version, but now 28 is being released, and will be followed by 29, 30, etc - bumping an epoch makes the devel version greater than any released version. Making 'devel' part of the version makes it explicit that this is not a supported version. Signed-off-by: Renan Rodrigo <[email protected]>
Signed-off-by: Renan Rodrigo <[email protected]>
lucasmoura
force-pushed
the
release-29
branch
2 times, most recently
from
06000d6
to
fd01fd1
Compare
renanrodrigo
approved these changes
Aug 1, 2023
orndorffgrant
approved these changes
Aug 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.