Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

rapidpro / mailroom Public

Notifications You must be signed in to change notification settings
Fork 29
Star 26

Code
Issues 15
Pull requests 1
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Resolve flows and groups to ids for elastic queries#614

Merged

rowanseymour merged 5 commits intomainrapidpro/mailroom:mainfrom es_asset_idsrapidpro/mailroom:es_asset_idsCopy head branch name to clipboard

Apr 6, 2022

+169-46

Conversation Commits5 (5)Checks Files changed

Commits

Commits on Apr 4, 2022

Update to latest goflow which requires mapping groups and flows to ids for ES queries
rowanseymour
committed
Merge branch 'main' into es_asset_ids
rowanseymour
committed
Fix tests
rowanseymour
committed

Commits on Apr 5, 2022

Fix mapping of flow assets to their IDs
rowanseymour
committed
Fix logging statement
rowanseymour
committed

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.