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: enable self service notification support #2930

Merged
merged 20 commits into from
Aug 8, 2023

Conversation

zachaller
Copy link
Collaborator

@zachaller zachaller commented Aug 2, 2023

Allow rollouts to define configuration for notification engine in the namespace of the rollout resource.

Related docs improvement issue as well since notification docs are so light: #2945

Signed-off-by: zachaller <zachaller@users.noreply.github.com>
Signed-off-by: zachaller <zachaller@users.noreply.github.com>
Signed-off-by: zachaller <zachaller@users.noreply.github.com>
Signed-off-by: zachaller <zachaller@users.noreply.github.com>
Signed-off-by: zachaller <zachaller@users.noreply.github.com>
Signed-off-by: zachaller <zachaller@users.noreply.github.com>
Signed-off-by: zachaller <zachaller@users.noreply.github.com>
Signed-off-by: zachaller <zachaller@users.noreply.github.com>
Signed-off-by: zachaller <zachaller@users.noreply.github.com>
…service-zaller

Signed-off-by: zachaller <zachaller@users.noreply.github.com>
…service-zaller

Signed-off-by: zachaller <zachaller@users.noreply.github.com>
Signed-off-by: zachaller <zachaller@users.noreply.github.com>
@zachaller zachaller changed the title feat: self service notifications eat: enable self service notification support Aug 2, 2023
@zachaller zachaller changed the title eat: enable self service notification support feat: enable self service notification support Aug 2, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Aug 2, 2023

Go Published Test Results

2 033 tests   2 033 ✔️  2m 40s ⏱️
   118 suites         0 💤
       1 files           0

Results for commit d2e1cd9.

♻️ This comment has been updated with latest results.

@codecov
Copy link

codecov bot commented Aug 2, 2023

Codecov Report

Patch coverage: 90.90% and project coverage change: -0.01% ⚠️

Comparison is base (d27d285) 81.75% compared to head (d2e1cd9) 81.74%.
Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2930      +/-   ##
==========================================
- Coverage   81.75%   81.74%   -0.01%     
==========================================
  Files         133      133              
  Lines       20336    20339       +3     
==========================================
+ Hits        16625    16627       +2     
- Misses       2855     2856       +1     
  Partials      856      856              
Files Changed Coverage Δ
utils/record/record.go 79.66% <58.33%> (-0.42%) ⬇️
controller/controller.go 89.64% <100.00%> (+0.11%) ⬆️

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

@github-actions
Copy link
Contributor

github-actions bot commented Aug 2, 2023

E2E Tests Published Test Results

    4 files      4 suites   3h 31m 34s ⏱️
102 tests   90 ✔️   6 💤   6
418 runs  384 ✔️ 24 💤 10

For more details on these failures, see this check.

Results for commit d2e1cd9.

♻️ This comment has been updated with latest results.

Signed-off-by: zachaller <zachaller@users.noreply.github.com>
Signed-off-by: zachaller <zachaller@users.noreply.github.com>
@zachaller zachaller requested a review from leoluz August 3, 2023 16:36
Signed-off-by: zachaller <zachaller@users.noreply.github.com>
person who can configure notifications in that namespace generally. However, in some cases, it is required to allow end-users to configure notifications
for their Rollout resources. For example, the end-user can configure notifications for their Rollouts in the namespace where they have access to and their rollout is running in.

To use this feature all you need to do is create the same configmap named `argo-rollouts-notification-configmap` and possibly
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe add a link to where this configmap is defined so users have a easy reference to how this configmap is supposed to look like

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

In context of the rest of the doc I think the idea of the config map is explained: https://argo-rollouts.readthedocs.io/en/stable/features/notifications/

Copy link
Contributor

Choose a reason for hiding this comment

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

The documentation mentions about the argo-rollouts-notification-configmap and shows some simple examples. I think that we should provide a link to the configmap definition with all possible fields it can have. Looking at the doc , I couldn't find such info easily. Is there a place users can look to see the full reference doc?

Signed-off-by: zachaller <zachaller@users.noreply.github.com>
@sonarcloud
Copy link

sonarcloud bot commented Aug 3, 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
16.2% 16.2% Duplication

Copy link
Contributor

@leoluz leoluz left a comment

Choose a reason for hiding this comment

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

LGTM

@zachaller zachaller merged commit e1c6136 into argoproj:master Aug 8, 2023
23 checks passed
@zachaller zachaller deleted the self-service-zaller-flag branch August 8, 2023 15:50
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