-
Notifications
You must be signed in to change notification settings - Fork 144
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
Adding secrets field and refactoring the logging process. #667
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
fokion
force-pushed
the
feat/remove-secrets
branch
from
May 12, 2023 22:41
f5fc880
to
bf48e00
Compare
fokion
changed the title
wip - Adding secrets field and refactoring the logging process.
Adding secrets field and refactoring the logging process.
May 12, 2023
fokion
force-pushed
the
feat/remove-secrets
branch
from
May 17, 2023 22:28
7b775a1
to
17b42e1
Compare
fokion
force-pushed
the
feat/remove-secrets
branch
4 times, most recently
from
June 5, 2023 20:53
d5a444c
to
c28e105
Compare
fokion
force-pushed
the
feat/remove-secrets
branch
from
June 7, 2023 12:31
c28e105
to
2d3a4f6
Compare
let me know if that can be merged :) |
fokion
force-pushed
the
feat/remove-secrets
branch
from
June 7, 2023 18:44
2d3a4f6
to
c28e105
Compare
…ets in the context and creating a function that we can call to hide sensitive data Add the ability to set secrets in the testsuite Signed-off-by: Fokion Sotiropoulos <[email protected]>
Signed-off-by: Fokion Sotiropoulos <[email protected]>
Signed-off-by: Fokion Sotiropoulos <[email protected]>
Signed-off-by: Fokion Sotiropoulos <[email protected]>
yesnault
force-pushed
the
feat/remove-secrets
branch
from
July 17, 2023 15:40
c28e105
to
ab98715
Compare
fokion
added a commit
to fokion/venom
that referenced
this pull request
Aug 1, 2023
) * adding secrets field and refactoring the logging process. Adding secrets in the context and creating a function that we can call to hide sensitive data Signed-off-by: Fokion Sotiropoulos <[email protected]> Co-authored-by: Yvonnick Esnault <[email protected]> Signed-off-by: Fokion Sotiropoulos <[email protected]>
ivan-velasco
pushed a commit
to socotra/venom
that referenced
this pull request
Sep 20, 2023
) * adding secrets field and refactoring the logging process. Adding secrets in the context and creating a function that we can call to hide sensitive data Signed-off-by: Fokion Sotiropoulos <[email protected]> Co-authored-by: Yvonnick Esnault <[email protected]> Signed-off-by: Ivan Velasco <[email protected]>
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.
Adding secrets in the context and creating a function that we can call to hide sensitive data
Add the ability to mark variables as secrets in the testsuite so that the venom.log does not show them
#476