Ulises Cervino
02/22/2024, 6:19 PM--ignore
hoping that this would ignore the integration altogether, but that doesn’t seem to be the case. Other than bypassing can-i-deploy
until they deploy to prod, what options do I have? context: I know it’s safe to deploy to prod without this dependency, etc. Thanks in advance.Christopher Tonog
02/27/2024, 3:42 AMNote: this contract could not be parsed to a v1 or v2 Pact, showing raw content instead.
It's using the Pact V4 version, not sure if there's a flag I need to set or specific version I need to deploy in order to get the UI to be more human readable? Thank you!Konstantin Manna
02/28/2024, 1:58 PMpact-broker publish
fails and returns exit code 1: How to figure out what is the reason for it to fail? It does not output anything (Version 1.68.0)Laurence Cruz
02/29/2024, 2:32 AMlatest
?
I’m specifically talking about having these link out to a mainline `master`/`main` tag ? Hope my question makes sense, can 🧵 for more context.Endika
03/01/2024, 10:38 AMpb:publish-verification-results
. I see in the documentation that the body to be sent is this:
{
"success": true,
"providerApplicationVersion": "1.0.1",
"buildUrl": "<http://my-ci.org/build/3456>"
}
Is it possible to send the following variables
{
"success": true,
"providerApplicationVersion": "1.0.1",
"providerVersionTags": [
"development"
],
"branch": "my-branch"
}
so that the Broker can store that information?ralph van der horst
03/01/2024, 8:01 PMralph van der horst
03/01/2024, 8:04 PMralph van der horst
03/01/2024, 8:05 PMBen Brugman
03/04/2024, 3:17 PMpact-broker \
can-i-deploy \
--pacticipant=IOSConsumer \
--latest
--pacticipant=AndroidConsumer \
--latest
--broker-base-url=<https://pact-broker.com/feature> \
--to-environment=PROD
But it feels like a lot of maintenance to always have all your pacticipants up to date.
So in short, which answer applies most
1. We are mis-using Can-I-Deploy.
2. We are doing it right and should take care of managing all the pacticipants on multiple brokers.
3. We Should run all pacticipants of one broker at once, and we missed some pact functionalityAna Osorio
03/05/2024, 3:42 AMcontract_content_changed
. In the webhook's body, I send the necessary information to initiate the provider build.
See the webhook in the 🧵.
Is there a way to obtain not only the consumerVersionBranch
but also the consumer's base branch? Something like: "consumerBaseBranch": "${pactbroker.consumerVersionBaseBranch}"
. Any ideas? Thanks in advance.Laurence Cruz
03/05/2024, 9:25 PM/metrics
endpoint. We've got an internal instance of a pact broker and it shows a total of 8 unique "pacticipants" but I'm getting 12. I'm curious if I'm just misunderstanding what a pacticipant is or if there's something I'm missing.
I'm also wondering if it's some cache/DB issue?
"pacticipants": {
"count": 12,
"withMainBranchSetCount": 5
},
Dmitry Munda
03/07/2024, 4:25 PMDominic Behrig
03/07/2024, 5:36 PMDhaval Dongre
03/12/2024, 2:29 PMFor security purposes, the response details are not logged. To enable response logging, configure the webhook_host_whitelist property
We are using a pact-broker chart and have explicitly set the webhookHttpMethodWhitelist
value to "POST". Any idea why I might be seeing this issue despite creating the whitelist?AlanB
03/21/2024, 1:22 PMpb:error-logs
for a webhook?
We've hit on occasions where a webhook has a problem, e.g. incorrect pipeline ID has been supplied when creating the webhook, which results in a legitimate error. Because the pipeline cannot be found.
When correcting such an issue (correcting the pipeline id) the error logs are still present.
Is there any way to clear these logs? Or do they only clear when the webhook (with the new pipeline ID) is successfully triggered for its event (contract_requiring_verification_published
) ?
Manually triggering the webhook, does not clear the error log either.
ThanksMarcus Hsu
03/21/2024, 2:51 PMMarcus Hsu
03/21/2024, 3:45 PMMartin Gallauner
03/25/2024, 2:28 PMrecord-deployment
work. But it tells me that the requested document was not found on this server.
What I did:
• pact-broker publish
returns published successfully and gives me an url where to find my pact. something like view the pubished pact at <http://broker.pactflow.io/pacts/provider/{providerName}/consumer/{consumerName}/version/{gitHash}|broker.pactflow.io/pacts/provider/{providerName}/consumer/{consumerName}/version/{gitHash}>
• pact-broker record-deployment
returns Error making request to <http://broker.pactflow.io/pacticipants/{consumerName}/versions|broker.pactflow.io/pacticipants/{consumerName}/versions>
should I be concerned about the difference of the url they publish to or search the pact from?
If yes, what is should be the pacticipant
parameter when running pact-broker record-deployment
?
Thanks!Chris
03/28/2024, 1:12 AMcan-i-merge
when working out of a monorepo? more details below.Ben Brugman
04/02/2024, 7:35 AMAshley Gautama
04/03/2024, 12:28 PMJamesC
04/05/2024, 10:00 AMZied Bejaoui
04/05/2024, 11:30 AM"test:publish": "pact-broker publish ./pacts --consumer-app-version=\"$(npx absolute-version)\" --auto-detect-version-properties --broker-base-url=https://*****.<http://pactflow.io|pactflow.io> --broker-token=***********"
Ben Brugman
04/09/2024, 3:43 PM--user=tokenuuid
This did the trick!
We are setting up webhooks, we want to use Basic Auth and pass our Token without a username. so --user='':'tokenuuid'
This gives us a 302 not found, but if we use the same token in an encrypted fashion via the --header='Authorization:Basic ecryptedtokenuuid
(Postman gives us this encrypted token)
We get a 200. are we doing something wrong? we tried alot of things already like:
• --user=':tokenuuid'
• --user=:tokenuuid
• --user='':'tokenuuid'
Charlan Bettiol
04/10/2024, 6:06 PMenvironment:
SSL_CERT_FILE: /Users/charlan.bettiol/Documents/certificados/_.livelo.intranet.cer
PACT_BROKER_PORT: '9292'
PACT_BROKER_DATABASE_URL: "<postgres://postgres:password@postgres/postgres>"
PACT_BROKER_LOG_LEVEL: DEBUG
PACT_BROKER_LOG_FORMAT: color
PACT_BROKER_SQL_LOG_LEVEL: DEBUG
PACT_BROKER_HTTP_DEBUG_LOGGING_ENABLED: true
PACT_BROKER_DISABLE_SSL_VERIFICATION: true
PACT_BROKER_BASIC_AUTH_ENABLED: true
PACT_BROKER_BASIC_AUTH_USERNAME: teste
PACT_BROKER_BASIC_AUTH_PASSWORD: 1234
command:
pact-broker list_environments -b <http://localhost:9292> --broker-username=teste --broker-password=1234
Charlan Bettiol
04/10/2024, 6:07 PMError making request to <http://localhost:9292> status=400
Charlan Bettiol
04/11/2024, 1:43 PMexport const ExampleFetchComponent = () => {
const classes = useStyles();
const { value, loading, error } = useAsync(async () => {
// Simulação de uma chamada assíncrona para obter a URL do iframe
// Você pode substituir isso por sua lógica real
const url = '<http://localhost:9292/>';
return url;
}, []);
if (loading) {
return <Progress />;
} else if (error) {
return <ResponseErrorPanel error={error} />;
}
// Renderizar o iframe
return (
<div className={classes.iframeContainer}>
<iframe
className={classes.iframe}
src="<http://localhost:9292/>"
title="Iframe Example"
allow="fullscreen"
/>
</div>
);
};
Rouaa Ben Ayed
04/11/2024, 3:50 PMEvan Rademacher
04/17/2024, 4:23 PMAdam Witko
04/24/2024, 12:38 PMcontract_requiring_verification_published
event with url <https://gitlab.com/api/v4/projects/${PROJECT_ID}/ref/${BRANCH}/trigger/pipeline?token=${TOKEN}&variables[PACT_URL]=>\${pactbroker.pactUrl}&variables[PACT_PROVIDER_VERSION]=\${pactbroker.providerVersionNumber}&variables[PACT_PROVIDER_BRANCH]=\${pactbroker.providerVersionBranch}
. For some reason when the broker triggers the pipeline it specifies a provider version number for the version of the provider at time of webhook creation and not for the latest main version of the provider. When the provider is deployed to an env it is recording the deployment with the git short sha for the commit and the latest main is months ahead of the version specified as PACT_PROVIDER_VERSION
.
I'm on version 2.102.2
of the broker.
I have a sneaking suspicion that because the verification job does not have the correct provider version that it's unable to offer the pre-verifier support to contracts.