Skip to content
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

Dry run should check the remote urls #52

Closed
fntlnz opened this issue Apr 15, 2020 · 4 comments
Closed

Dry run should check the remote urls #52

fntlnz opened this issue Apr 15, 2020 · 4 comments
Labels
kind/feature New feature or request lifecycle/rotten

Comments

@fntlnz
Copy link
Contributor

fntlnz commented Apr 15, 2020

Motivation

We have a flag to execute driverkit in a dry run mode that actually only validates the parameters.
Since driverkit heavily depends on the correctness of the parameters passed to download the correct kernel headers/source for the current distribution it seems right to me that dry run also checks the remote URLs for the existence of the resources without downloading the final artifacts. In this way, we can run driverkit against a list of files and be confident that they will work before doing the beefy builds.

Feature

See motivation

Alternatives

Be blind

Additional context

This is needed to allow the test-infra build grid have a test step in the PRs without doing the builds every time.

@poiana
Copy link

poiana commented Nov 20, 2020

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

@poiana
Copy link

poiana commented Dec 24, 2020

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

@poiana
Copy link

poiana commented Jan 24, 2021

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana
Copy link

poiana commented Jan 24, 2021

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@poiana poiana closed this as completed Jan 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request lifecycle/rotten
Projects
None yet
Development

No branches or pull requests

2 participants