squash! make varlink optional for podman #2
Merged
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
wking
force-pushed
the
varlink-optional-command-cleanup
branch
from
ab5f906 to
d558685
Compare
The command-pointer approach will scale well if/when we add additional optional commands behind their own build tags, because those tags won't all be competing for the same getOptionalCommands namespace. Signed-off-by: W. Trevor King <[email protected]>
wking
force-pushed
the
varlink-optional-command-cleanup
branch
from
d558685 to
6a86956
Compare
baude
added a commit
that referenced
this pull request
Jul 30, 2018
This is the second round of performance improvements for out integration tests. Signed-off-by: baude <[email protected]>
baude
added a commit
that referenced
this pull request
Jul 30, 2018
This is the second round of performance improvements for out integration tests. Signed-off-by: baude <[email protected]> Closes: containers#1190 Approved by: rhatdan
baude
pushed a commit
that referenced
this pull request
Mar 13, 2019
Signed-off-by: TomSweeneyRedHat <[email protected]> Vendors in fsouza/docker-client, docker/docker and a few more related. Of particular note, changes to the TweakCapabilities() function from docker/docker along with the parse.IDMappingOptions() function from Buildah. Please pay particular attention to the related changes in the call from libpod to those functions during the review. Passes baseline tests.
baude
pushed a commit
that referenced
this pull request
Mar 13, 2019
…/bigvendorbuildah2 Vendor docker/docker, fsouza and more #2
baude
pushed a commit
that referenced
this pull request
Jul 10, 2019
It's desirable to make archives available of builds containing actual
tested content. While not official distro-releases, these will enable
third-party testing, experimentation, and development for both branches
(e.g. "master") and pull requests (e.g. "pr3106").
* Add a Makefile targets for archiving both regular podman binaries
and the remote-client. Encode release metadata within these
archives so that their exact source can be identified.
* Fix bug with cross-compiling remote clients for the Windows and Darwin
platforms.
* Add unit-testing of cross-compiles for Windows and Darwin platforms.
* A few small CI-script typo-fixes
* Add a script which operates in two modes:
1. Call Makefile targets which produce release archives.
Upload the archive to Cirrus-CI's built-in caching system
using reproducible cache keys.
2. Utilize reproduced cache keys to attempt download of cache
from each tasks. When successful, parse the file's
release metadata, using it to name the archive file. Upload
all recovered archives to a publicly accessible storage bucket
for future reference.
* Update the main testing task to call the script in mode #1 for
all primary platforms.
* Add a new `$SPECIALMODE` task to call the script in mode #1 for
Windows and Darwin targets.
* Add a new 'release' task to the CI system, dependent upon all other
tasks. This new tasks executes the script in mode #2.
* Update CI documentation
Signed-off-by: Chris Evich <[email protected]>
baude
added a commit
that referenced
this pull request
Jan 23, 2020
Add API review comments to correct documentation and endpoints. Also, add a libpode prune method to reduce code duplication. Only used right now for the API but when the remote client is wired, we will switch over there too. Signed-off-by: Brent Baude <[email protected]>
baude
pushed a commit
that referenced
this pull request
Feb 19, 2020
As I've mentioned once or twice, hand-maintained swagger docs
are evil. This commit attempts to fix:
* Inconsistent methods (swagger says POST but code signature
says GET)
* Inconsistent capitalization
* Typos ("Mounter", "pood")
* Completely wrong paths (/inspect vs /json)
* Missing .Method() registrations
* Missing /libpod in some /volumes paths
* Incorrect method declaration: /libpod/containers/.../kill
was correct (POST) in swagger but wrong in the code itself
(http.MethodGet). Correct the latter to MethodPost
This is two hours' work, even with a script I have that
tries to cross-check everything.
Swagger docs should not be human-maintained.
Signed-off-by: Ed Santiago <[email protected]>
baude
pushed a commit
that referenced
this pull request
Feb 19, 2020
Swagger: fix inconsistencies (try #2)
baude
pushed a commit
that referenced
this pull request
Jan 25, 2022
Signed-off-by: Daniel J Walsh <[email protected]>
baude
pushed a commit
that referenced
this pull request
Jan 25, 2022
Fix #2 for compat commit handling of --changes
baude
added a commit
that referenced
this pull request
Jul 11, 2023
* Use vfkit command line assembly * Inject ignition file into guest using http over vsock * Ready notification through use of vsock [NO NEW TESTS NEEDED] Signed-off-by: Brent Baude <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The command-pointer approach will scale well if/when we add additional optional commands behind their own build tags, because those tags won't all be competing for the same
getOptionalCommandsnamespace.