Followup ros2 expired keyring #15
Merged
Conversation
This file contains hidden or 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
GuillaumeLaine
force-pushed
the
followup-ros2-expired-keyring
branch
3 times, most recently
from
63aaa7f to
3779c42
Compare
GuillaumeLaine
force-pushed
the
followup-ros2-expired-keyring
branch
from
3779c42 to
eded63f
Compare
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.
Follow-up to #14
The ros2 key rotation did not work on ubuntu 20.04 because it stores the key in a different location. This fixes that.
Testing
Tested a full CI run this time to avoid more surprises: https://github.com/Auterion/auterion-sdk/pull/136
apt updateis running OK. CI is failing because of the known issue with missing fastrtps_cmake_module.