👋 , i tried to search the documentation for more info about environments, but i couldnt find anything to help describe the option

--no-production

for the cli

pact-broker create-environment

, documented here. is this option purely informational when creating an environment, or is it used somewhere like provider verification?

This is a great question! I don't know the answer, but I did notice that that document links to itself for more information:

The "test" and "production" environments will have been seeded for you. You can check the existing environments by running pact-broker list-environments. See https://docs.pact.io/pact_broker/client_cli/readme#environments for more information.

It’s just whether or not the environment is a production environment.

yep, definitely more clear there. i looked in the cli doc first, so 👍 from me. fwiw, i was partly wondering if i could use it with

can-i-deploy

as a way to check many environments containing

production = true

tell me more about that usecase @Hazem Borham

so we have a canonical environment pipeline for our micro service deployment:

dev-> stg -> prd

using the pact broker, i created the three envs. two with the field

production=true

, eg stg and prd. dev has the field

production=false

. this was due to me not knowing this flag was purely informational. after merge to main, we were thinking our AWS codepipeline as such:

#dev
can-i-deploy --environment=dev --dry-run 
deploy
record-deployment --environment=dev

#stg
can-i-deploy --environment=stg
deploy
record-deployment --environment=stg

#prod
can-i-deploy --environment=stg
deploy
record-deployment --environment=stg

in our pr pipeline, we wanted to verify can-i-deploy would work for all of our production env:

test
can-i-deploy --environment=stg
can-i-deploy --environment=prd

then it crossed my mind that the

--production --no-production

flags i came across during the create-environment might have special meaning. so i asked in this thread. :) basically i was curious if i could do this instead:

test
can-i-deploy --to-production-environments

Thanks! That makes sense.