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

Add better support for workflows that are managed by feature toggles (rather than branches) #684

Open
canny bot opened this issue Jun 26, 2024 · 2 comments

Comments

@canny
Copy link

canny bot commented Jun 26, 2024

The current domain model in the Pact Broker supports git branch based workflows, however it does not provide good support for feature toggle based workflows. One example of this is that you can only have one pact per consumer version/provider. A team using feature toggles may wish to have different pacts (or potentially different sets of interactions within a pact) for each feature toggle, for the same consumer version.

https://pact.canny.io/admin/board/feature-requests/p/add-better-support-for-workflows-that-are-managed-by-feature-toggles-rather-than

Copy link
Author

canny bot commented Jun 26, 2024

This issue has been linked to a Canny post: Add better support for workflows that are managed by feature toggles (rather than branches) 🎉

@YOU54F
Copy link
Member

YOU54F commented Jun 27, 2024

Matt Fellows - Feb 9, 2022

See also this conversation: https://pact-foundation.slack.com/archives/C5F4KFKR8/p1644368136519989
I think we could also look to address trunk-based workflows in documentation in the meantime also.

Beth - July 12, 2021

There is no explicit support for this yet, but I have documented a workflow to use features with tags here https://docs.pact.io/pact_broker/tags/#using-tags-with-feature-toggles-instead-of-feature-branches

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

No branches or pull requests

1 participant