A DevOps Project whose Pushes Build, on Your Network

The project, repository and pipeline are separate resources and none reacts to a commit until a trigger ties a push to the pipeline; builds run as the DevOps service and fail on the first step without a dynamic group and policy; and the runner is on Oracle's network unless given a subnet. Trigger created, runner attached to your subnet, and the IAM rule and statements exported.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Nothing else in the catalogue covers ci/cd & automation on Oracle Cloud. If this module is not the right shape, the closest options are on other clouds.

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "oci_devops" {
  source  = "www.iac-bazaar.com/iac-bazaar/oci-devops/oci"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.