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

Enable read-events feature in dev/staging by default #4591

Merged
merged 5 commits into from
Sep 3, 2024
Merged

Conversation

awwaiid
Copy link
Collaborator

@awwaiid awwaiid commented Aug 11, 2024

We have manually enabled this in production.

We have manually enabled this in production
@awwaiid awwaiid requested a review from dorner August 11, 2024 15:01
dorner
dorner previously approved these changes Aug 16, 2024
@dorner
Copy link
Collaborator

dorner commented Aug 16, 2024

So I think we need to change the code here:

if ENV['EVENTS_READ'] == 'true'

Right now it only forces true if the env variable is true. I think we need to force false if it's not true.

Copy link
Collaborator

@dorner dorner left a comment

Choose a reason for hiding this comment

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

.

@awwaiid awwaiid requested a review from dorner August 21, 2024 00:21
@awwaiid
Copy link
Collaborator Author

awwaiid commented Aug 21, 2024

Right now it only forces true if the env variable is true. I think we need to force false if it's not true.

I made a further change that removes this, and then event-mode github actions, altogether

@@ -170,12 +170,6 @@ def self.capybara_tmp_path
Capybara.server = :puma, { Silent: true }
end

config.before(:each) do
if ENV['EVENTS_READ'] == 'true'
allow(Event).to receive(:read_events?).and_return(true)
Copy link
Collaborator

Choose a reason for hiding this comment

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

I don't think we can do this - even though we're setting it to true in the seeds, it won't be set to true in the actual tests. If we want to always run it with true, we should just remove lines 174 and 176 and leave the rest in.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Oh right ... seeds lot loaded in specs. I forgot. OK -- I'm putting that back. I think another week or two and we should remove all of the remaining feature-flag related things for Events, but we can do that separately.

This is needed just a bit longer until we completely remove the feature
flag for Events
@awwaiid awwaiid requested a review from dorner August 24, 2024 20:11
Copy link
Collaborator

@dorner dorner left a comment

Choose a reason for hiding this comment

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

@awwaiid this looks good to me - but based on the issue last week, are we sure we are ready for this? Do we want to wait a bit longer?

@awwaiid
Copy link
Collaborator Author

awwaiid commented Sep 2, 2024

I'm sure! No going back! The issue last week is likely exactly the sort of issue we have without Events except without Events it is untracable and unfixable.

@cielf
Copy link
Collaborator

cielf commented Sep 3, 2024

I agree with Brock -- I really don't think we're going back at this point. I'm not quite ready to rip out the old stuff entirely , but we should have what developers are working with by default be what the banks are working with.

@dorner dorner merged commit d83c6dc into main Sep 3, 2024
23 checks passed
@dorner dorner deleted the enable-read-events branch September 3, 2024 15:19
@dorner
Copy link
Collaborator

dorner commented Sep 3, 2024

On we go then!

ewoknock pushed a commit to ewoknock/human-essentials that referenced this pull request Sep 3, 2024
* Enable read-events feature in dev/staging by default

We have manually enabled this in production

* Remove more Event Sourcing separation

* Minor documentation whitespace cleanup

* Put back read_events check in specs

This is needed just a bit longer until we completely remove the feature
flag for Events
Copy link
Contributor

github-actions bot commented Sep 8, 2024

@awwaiid: Your PR Enable read-events feature in dev/staging by default is part of today's Human Essentials production release: 2024.09.08.
Thank you very much for your contribution!

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