CICD support for Bitbucket Repository

[HarshalSanap007]

Hey @ludoo ,
Do we have the CICD implementation support for Bitbucket repo and Cloudbuild as CICD tool?

[ludoo]

There was some work last year to add Bitbucket support but it stalled. Cloud build we used to have, we dropedd support once GCP Source Repos were deprecated. We might reconsider both if there's actual need, of course.

[ludoo]

you should use the providers file and service account we generate...

[HarshalSanap007]

bootstrap needs to be run manually at least the first two times: first as a user, then as the service account with providers/backend file in place

after that you can plug it into a repo/pipeline

Does that means it should not be deployed as CICD from start, once all resource are created further customizations can be part of CICD , is that what you mean here?

Thanks?

[HarshalSanap007]

you should use the providers file and service account we generate...

This I'm trying to add for bootstrap process .

[ludoo]

Sorry I can't follow what you're writing. Just make sure you go through the flow describe in the bootstrap stage documentation, without devising your own method to deploy it which won't work and we don't support.

[HarshalSanap007]

Extremly sorry that you got confused here

[HarshalSanap007]

I Might have confused you - I will try to explain again here-
So I want to create landing zone with fast fabric modules, I've tried each step manually like going to each stage and doing terraform init and apply I've applied and created resources for every stage .
Now Im trying to achieve this same with CICD deployment creating individual repo for each stage so -
my questions -
1: Do we need to run 0-bootstrap stage manually or it can be directly run under CICD?
2: If we can run under CICD , as we are migrating the state from local location "fast-config" to iac bucket, instead of local outputs location can we directly pass remote location "outputs_location = "~/fast-config-ofw"?

[ludoo]

You need to have a working bootstrap already set up, and configure the cicd variable. Once you do that we create additional service accounts, and the workflow files for Github or Gitlab.

State is always in the same GCS bucket. Fast config is used for output/provider files, but the same files exist in the GCS outputs bucket and are fetched from there by the workflows. You should not use outputs_location once you switch to CI/CD.

Again, please read through our docs. :)

[HarshalSanap007]

Thanks it helped