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

feat(controller): Add custom metadata support for AnalysisRun. Fixes #2740 #2743

Merged

Conversation

lukaszgyg
Copy link
Contributor

@lukaszgyg lukaszgyg commented Apr 24, 2023

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
  • The title of the PR is (a) conventional with a list of types and scopes found here, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
  • I've signed my commits with DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My builds are green. Try syncing with master if they are not.
  • My organization is added to USERS.md.

@lukaszgyg
Copy link
Contributor Author

This PR is the implementation for #2740

@github-actions
Copy link
Contributor

github-actions bot commented Apr 24, 2023

Go Published Test Results

1 950 tests   1 950 ✔️  2m 37s ⏱️
   118 suites         0 💤
       1 files           0

Results for commit ec61e59.

♻️ This comment has been updated with latest results.

@codecov
Copy link

codecov bot commented Apr 24, 2023

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (04b1e30) 81.62% compared to head (ec61e59) 81.63%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2743   +/-   ##
=======================================
  Coverage   81.62%   81.63%           
=======================================
  Files         133      133           
  Lines       20157    20163    +6     
=======================================
+ Hits        16454    16460    +6     
  Misses       2849     2849           
  Partials      854      854           
Impacted Files Coverage Δ
rollout/analysis.go 80.96% <100.00%> (+0.33%) ⬆️

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@lukaszgyg lukaszgyg force-pushed the add-custom-analysisrun-metadata branch from 0daf4cd to c2b9846 Compare April 24, 2023 16:58
@github-actions
Copy link
Contributor

github-actions bot commented Apr 24, 2023

E2E Tests Published Test Results

    4 files      4 suites   3h 22m 41s ⏱️
  96 tests   85 ✔️   5 💤   6
400 runs  364 ✔️ 20 💤 16

For more details on these failures, see this check.

Results for commit ec61e59.

♻️ This comment has been updated with latest results.

@lukaszgyg lukaszgyg force-pushed the add-custom-analysisrun-metadata branch 4 times, most recently from daa94be to 14bfaec Compare April 24, 2023 23:09
@lukaszgyg lukaszgyg marked this pull request as draft April 25, 2023 05:58
@lukaszgyg lukaszgyg force-pushed the add-custom-analysisrun-metadata branch from 14bfaec to e9c230e Compare April 25, 2023 06:06
@lukaszgyg lukaszgyg marked this pull request as ready for review April 25, 2023 07:00
@zachaller
Copy link
Collaborator

Will give this a code review in just a bit, but in the meantime can you also add to the spec docs https://argoproj.github.io/argo-rollouts/features/specification/

@lukaszgyg lukaszgyg force-pushed the add-custom-analysisrun-metadata branch from e9c230e to a8a44ec Compare April 27, 2023 18:30
@lukaszgyg
Copy link
Contributor Author

@zachaller I added the docs spec. Can you review the PR?

@sonarcloud
Copy link

sonarcloud bot commented May 4, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 1 Code Smell

No Coverage information No Coverage information
1.7% 1.7% Duplication

@alexef
Copy link
Member

alexef commented May 26, 2023

@zachaller I assume this will be part of 1.6, not sooner, or?

@zachaller
Copy link
Collaborator

@alexef Yea it would be a new feature not a bug fix so would go in 1.6

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.

3 participants