cf-ops-automation
cf-ops-automation copied to clipboard
a collaboration framework for operating cloudfoundry and services at scale
A lot of [concourse tasks](https://github.com/orange-cloudfoundry/cf-ops-automation/tree/develop/concourse/tasks) launch a shell script. We should refactor theses shell scripts to ruby, to have a better unit tests support. We can focus on task not...
The paas-template repo aims at being public (at least its main remote, see #62) with submodules fetching public github repos (such as [cf-deployment](https://github.com/cloudfoundry/cf-deployment)). COA needs to be able to operate...
[Terraform Cf provider](https://github.com/mevansam/terraform-provider-cf) provides a robust declarative support, which is more productive/expressive than the current bash-based support This is follow up of #28 This suport should also support smoke tests.
The cf-apps generated pipeline is not necessary in most root deployments, it is currently only useful on ops-deployment, and polutting on all other root deployments (coab, master, ops, micro ...)...
Introduces a `shared/models` dir in paas-templates to allow sharing across root deployment. Origin model could be described in `deployment-dependencies.yml` ``` --- deployment: bosh-ops: resources: template: base_path: ["shared/models/bosh"] secrets: ... ```...
https://www.terraform.io/docs/internals/debugging.html This is leveraged by https://github.com/orange-cloudfoundry/terraform-provider-cloudfoundry/#provider-configuration that can display CC_API verbose traces (equivalent of CF_TRACE=true) as well as recent app logs during app deployment (similar as #5) Note that terraform-resource...
Currently, bootstrapping a bosh director is a manual operation. The pipeline [micro-bosh-init-pipeline.yml](https://github.com/orange-cloudfoundry/cf-ops-automation/blob/develop/concourse/pipelines/micro-bosh-init-pipeline.yml) applies inception terraform and generates unused manifest. Some steps are missing to have a full bootstrap support. So...
This is a follow up of #40 and more generally the terraform pipelines * [ ] update unit tests to cover tf-pipeline.yml * [ ] set up TF data fixture...
Currently, application of terraform specs download the terraform binary and providers from internet, in a task, applying `sh -c "$(curl -fsSL https://raw.github.com/orange-cloudfoundry/terraform-provider-cloudfoundry/master/bin/install.sh)"` This is slow and vulnerable to failure when...
Possible content: The generated pipeline includes automatic merging of branch from the template and secrets git repos maching the regular expression develop,WIP-*,wip-*,feature-*, Feature-* see [source](https://github.com/orange-cloudfoundry/cf-ops-automation/blob/560214a0c34b0e80722cb48df58a714ac40ea1d5/concourse/pipelines/sync-feature-branches.yml#L42-L42) In case of merge conflict...