Braze regions server
Adds new regions to braze server destinations
Testing
- [ ] Added unit tests for new functionality
- [x] Tested end-to-end using the local server
- [ ] [If destination is already live] Tested for backward compatibility of destination. Note: New required fields are a breaking change.
- [ ] [Segmenters] Tested in the staging environment
- [ ] [Segmenters] [If applicable for this change] Tested for regression with Hadron.
@brennan can we get this merged please?
@marinhero any suggestions on what I need to do? Tests pass for me
Ah! I think the test snapshot might be out of date. Let's try these instructions. Let me know how it goes!
Also, looks like this was opened right in the middle of our node 22 update. Make sure you pull the latest version of the repo so that version of the CI checks can run.
Ah! I think the test snapshot might be out of date. Let's try these instructions. Let me know how it goes!
Do you have a public link?
@davidbielik Here it is: https://github.com/segmentio/action-destinations/blob/main/docs/testing.md#snapshot-testing
Hi @davidbielik, just checking in as the next deploy is scheduled for Tuesday April 8th and would be great to have this to be a part of it. LMK if you have any questions, I'll be happy to help. Best.
@marinhero I ran that command but no files change:
Tagging this weeks on-call to look into it @sayan-das-in
@davidbielik this appears to be a TZ issue. We either freeze the timezone within the tests or leave the prior value of the snapshot "2021-02-01". Freezing might be better for long term but keeping the old value will be a much quicker fix.
@davidbielik this appears to be a TZ issue. We either freeze the timezone within the tests or leave the prior value of the snapshot
"2021-02-01". Freezing might be better for long term but keeping the old value will be a much quicker fix.
Thanks - reverted date to the previous value.
Hi @marinhero, FYI I'm back so can run with this PR.
Tests pass locally and in CI. validate passes. Linter is complaining about this:
I'm going to create a new PR without this assertion, and will label it ready for deploy. I'll then close this PR.
Thanks @joe-ayoub-segment i removed those lines if that's easier