Skip to content

Autonomic Updates#3029

Open
clayandgen wants to merge 2 commits intomainfrom
autonomic-updates
Open

Autonomic Updates#3029
clayandgen wants to merge 2 commits intomainfrom
autonomic-updates

Conversation

@clayandgen
Copy link
Copy Markdown
Contributor

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 30, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.28%. Comparing base (ce4d8ea) to head (9324fcc).
⚠️ Report is 58 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3029      +/-   ##
==========================================
+ Coverage   78.26%   78.28%   +0.01%     
==========================================
  Files         673      673              
  Lines       55238    55263      +25     
  Branches      728      728              
==========================================
+ Hits        43234    43263      +29     
+ Misses      11926    11922       -4     
  Partials       78       78              
Flag Coverage Δ
python 79.48% <ø> (-0.01%) ⬇️
ruby-api 83.51% <100.00%> (-0.07%) ⬇️
ruby-backend 81.42% <100.00%> (+0.05%) ⬆️

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.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Copy Markdown
Member

@jmthomas jmthomas left a comment

Choose a reason for hiding this comment

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

I assume there is a companion enterprise PR to allow you name the triggers and reactions in the UI?

@jmthomas
Copy link
Copy Markdown
Member

I assume there is a companion enterprise PR to allow you name the triggers and reactions in the UI?

Yep I see you linked to it

def verify_triggers
# Validate that all triggers exist, but do not persist dependent changes yet.
# Returns the list of trigger models that need updating.
def validate_triggers_exist
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The change below is to ensure that the dependencies are not updated until after the trigger / reaction is created. This prevents an edge case where dependents are defined but the dependency doesn't exist.

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Apr 1, 2026

@clayandgen clayandgen requested a review from jmthomas April 2, 2026 14:54
Copy link
Copy Markdown
Member

@jmthomas jmthomas left a comment

Choose a reason for hiding this comment

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

So we're still able to create a unique name but it is fixed. If you want to change it you create a label. Feels like we can remove the name stuff.

name = hash.delete('name')
if name.nil? || name.strip.empty?
name = @model_class.create_unique_name(scope: params[:scope])
end
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do we need the name stuff anymore now that we're using the label field

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.

2 participants