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

fix(KFLUXBUGS-1342): add existing secret in the components secret form #61

Merged
merged 3 commits into from
Jan 23, 2025

Conversation

JoaoPedroPP
Copy link
Contributor

Fixes

KFLUXBUGS-1342

Description

When onboarding a new component and adding a build time secret, the dialog cannot find an existing secret in the workspace.

Copy link

codecov bot commented Jan 6, 2025

Codecov Report

Attention: Patch coverage is 90.32258% with 6 lines in your changes missing coverage. Please review.

Project coverage is 80.09%. Comparing base (4609b37) to head (0c62824).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
src/components/Secrets/SecretForm.tsx 80.00% 5 Missing ⚠️
src/components/Secrets/SecretModalLauncher.tsx 50.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #61      +/-   ##
==========================================
- Coverage   80.11%   80.09%   -0.02%     
==========================================
  Files         570      570              
  Lines       21452    21476      +24     
  Branches     5050     5062      +12     
==========================================
+ Hits        17187    17202      +15     
- Misses       4241     4250       +9     
  Partials       24       24              
Flag Coverage Δ
unittests 80.09% <90.32%> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@StanislavJochman
Copy link
Contributor

Let me know when you will have it ready. Will pull it and try it out.

@JoaoPedroPP JoaoPedroPP force-pushed the KONFLUX-5921 branch 3 times, most recently from f48167f to b8dafd3 Compare January 13, 2025 11:30
@sahil143
Copy link
Collaborator

/retest

@JoaoPedroPP JoaoPedroPP marked this pull request as ready for review January 13, 2025 17:00
@JoaoPedroPP
Copy link
Contributor Author

Codecov Report

Attention: Patch coverage is 90.32258% with 6 lines in your changes missing coverage. Please review.

Project coverage is 80.13%. Comparing base (1b04567) to head (b8dafd3).

Files with missing lines Patch % Lines
src/components/Secrets/SecretForm.tsx 80.00% 5 Missing ⚠️
src/components/Secrets/SecretModalLauncher.tsx 50.00% 1 Missing ⚠️
Additional details and impacted files

☔ View full report in Codecov by Sentry. 📢 Have feedback on the report? Share it here.

I believe this can be safely ignored

fix: list existing secret in build time secret modal

fix: adjust types in secret form
@marcin-michal
Copy link
Contributor

LGTM. Just wondering, is the smyk-secret always supposed to be an option? When adding a build secret to a component, it shows up as existing, even though I don't have it in the secrets list.

importSecrets?: ImportSecret[];
newSecrets?: string[];
importSecrets?: SecretFormValues[];
newSecrets?: ExistingSecret[];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO a little confusing when the newSecrets property has the type ExistingSecret

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch!
Changed to BuildTimeSecret

@JoaoPedroPP
Copy link
Contributor Author

LGTM. Just wondering, is the smyk-secret always supposed to be an option? When adding a build secret to a component, it shows up as existing, even though I don't have it in the secrets list.

The snyk-secret is special case that the user should always have the option to record, if it doesn't exist, or to use it

@StanislavJochman
Copy link
Contributor

LGTM

@JoaoPedroPP JoaoPedroPP added this pull request to the merge queue Jan 21, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Jan 21, 2025
@JoaoPedroPP JoaoPedroPP added this pull request to the merge queue Jan 21, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Jan 21, 2025
@JoaoPedroPP JoaoPedroPP added this pull request to the merge queue Jan 21, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Jan 21, 2025
@JoaoPedroPP JoaoPedroPP added this pull request to the merge queue Jan 21, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Jan 21, 2025
@testcara
Copy link
Contributor

LGTM

@JoaoPedroPP JoaoPedroPP added this pull request to the merge queue Jan 22, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Jan 22, 2025
@JoaoPedroPP JoaoPedroPP added this pull request to the merge queue Jan 22, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Jan 22, 2025
@JoaoPedroPP JoaoPedroPP added this pull request to the merge queue Jan 22, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Jan 22, 2025
@JoaoPedroPP JoaoPedroPP added this pull request to the merge queue Jan 22, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Jan 22, 2025
@JoaoPedroPP JoaoPedroPP added this pull request to the merge queue Jan 22, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Jan 22, 2025
@sahil143 sahil143 merged commit 92bda4a into konflux-ci:main Jan 23, 2025
5 checks passed
@JoaoPedroPP JoaoPedroPP mentioned this pull request Jan 23, 2025
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants