-
Notifications
You must be signed in to change notification settings - Fork 28
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
Use public API for vexination-walker #547
Comments
jcrossley3
added a commit
to jcrossley3/trustification
that referenced
this issue
Sep 19, 2023
Fixes trustification#547 Signed-off-by: Jim Crossley <jim@crossleys.org>
jcrossley3
added a commit
to jcrossley3/trustification
that referenced
this issue
Sep 19, 2023
Fixes trustification#547 Signed-off-by: Jim Crossley <jim@crossleys.org>
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 19, 2023
Fixes #547 Signed-off-by: Jim Crossley <jim@crossleys.org>
jcrossley3
added a commit
to jcrossley3/trustification
that referenced
this issue
Sep 20, 2023
Fixes trustification#547 again Signed-off-by: Jim Crossley <jim@crossleys.org>
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 21, 2023
Fixes #547 again Signed-off-by: Jim Crossley <jim@crossleys.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment the vexination-walker has direct access to s3 infrastructure, but we need to make it run using the public API. This allows us to run the walker processes externally and at a more appropriate time since we don't have access to s3 credentials outside the cluster.
The text was updated successfully, but these errors were encountered: