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

feat: publish provider contracts using all in one endpoint #141

Merged

Conversation

bethesque
Copy link
Member

No description provided.

"_links": {
"self": [
{
"href": "http://example.org/pacts/provider/Pricing%20Service/consumer/Condor/latest"

Choose a reason for hiding this comment

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

Good Ol' Condor and the Pricing Service

Copy link
Member Author

Choose a reason for hiding this comment

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

They'll always live on in our test data.

end
end
def enabled?
ENV.fetch("PACT_BROKER_FEATURES", "").include?("publish_provider_contracts_all_in_one")
Copy link
Member

Choose a reason for hiding this comment

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

Would the user set this?

will it say be set in the pact-cli and pact-ruby-standalone packages for the pactflow command, or are we expecting this to be used in testing for a bit and then we use the all in one?

Copy link
Member

Choose a reason for hiding this comment

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

why is the old way of publishing hanging around, whats the craic in general. is that meant to be phased out over time

Copy link
Member Author

Choose a reason for hiding this comment

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

The feature toggle is so we can use it internally for a few days before putting it out for public use. It's what I do for all our new commands. The code will be included in the docker images and ruby standalone as soon as I release it (today).

The old way is required because this is a brand new API, and our onprem customers will be using previous versions of Pactflow for who-knows-how-long. Some only update once a year or so.

Copy link
Member

Choose a reason for hiding this comment

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

Ok fabulous, that sounds like a really well considered approach, thanks for clarifying @bethesque


def initialize(params, options, pact_broker_client_options)
super
@provider_name = params[:provider_name]
@provider_version_number = params[:provider_version_number]
@branch_name = params[:branch_name]
@tags = params[:tags] || []
@build_url = params[:build_url]
Copy link
Member

Choose a reason for hiding this comment

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

nice addition.

@YOU54F
Copy link
Member

YOU54F commented Sep 6, 2023

Awesome looks great to me.

Just a reminder to me to update docs here

https://docs.pactflow.io/docs/bi-directional-contract-testing/publishing/

to include the build_url param

@bethesque
Copy link
Member Author

Thanks for the reminder. I forget that things are sprinkled around different parts of the docs now.

@bethesque bethesque merged commit a9f87a8 into master Sep 6, 2023
29 checks passed
@bethesque bethesque deleted the feat/publish-provider-contracts-using-all-in-one-endpoint branch September 6, 2023 23:23
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