Skip to content

feat(modules)!: sync Cloud Foundation Fabric modules to v60.0.0 and add sync tooling - #311

Merged
Calvin-Cheng1 merged 20 commits into
google:mainfrom
digitalresistor:feat/sync-cff-v59
Nov 9, 2026
Merged

Calvin-Cheng1 merged 20 commits into
google:mainfrom
digitalresistor:feat/sync-cff-v59

Conversation

@digitalresistor

@digitalresistor digitalresistor commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Description

The vendored modules under modules/ and the README tooling under tools/ now match upstream Cloud Foundation Fabric v59.2.0, and new tooling keeps them current with a weekly sync pull request. The modules last synced from Fabric v38.0.0, 21 major releases ago, so stages and blueprints missed upstream fixes and the move to google provider 8.

Fixes #308
Fixes #319

Sync tooling

  • The new tools/sync-from-cff.sh script three-way merges every file of every tracked module from its recorded base release to a target release, so Stellar Engine changes survive and conflicts surface instead of upstream overwriting them.
  • Each module records its base release in the module_name of its versions.tf file. The new tools/cff-sync.bases file covers the modules that upstream ships without one, and the -se copies track their upstream modules through the same records.
  • The tools/cff-sync.bases file also lists repository paths outside modules/, a directory or a single file, which the sync tracks the same way. The README tooling and the test fixtures use these entries.
  • Python files outside modules/ keep the repository ruff format style. The script formats both upstream sides the same way before it merges them, so the indentation difference from upstream never conflicts.
  • The script handles symbolic links as links, never writes through them, skips the paths in tools/cff-sync.ignore such as versions.tofu, and reports module calls to directories that do not exist.
  • Its report lists per-module results, Terraform and provider constraint changes, upstream modules that Stellar Engine does not vendor, and the upstream breaking changes since the base release.
  • The new .github/workflows/cff-sync.yml workflow runs the sync every Monday and keeps one pull request open through the new tools/cff-sync-pr.sh script. It opens the pull request as a draft when files conflict or a release needs a new provider major version.
  • The workflow never overwrites a sync branch that holds maintainer commits, such as conflict resolutions, and comments on the pull request once per new release instead.
  • With the conflict style that the workflow uses, a module with conflicts keeps its base release, so a later run with conflict markers merges the same files again.
  • The new docs/upstream-sync.md guide describes the procedure, the review checklist, the local changes that each sync preserves, the workflow setup and the cadence.
  • The new tests/test_sync_from_cff.sh and tests/test_cff_sync_pr.sh suites cover the merge paths, the tracked paths and the branch handling with throwaway repositories and a fake gh command. The tools/run_tests.sh script and the CI shell job run every tests/test_*.sh suite since refactor(tests): flatten test suite into tests/ and expand unit coverage #299.

Sync to v59.2.0

The commits separate the generated sync from the hand-written changes, so reviewers can check each one on its own.

  1. chore(modules): sync Cloud Foundation Fabric modules to v59.2.0 holds the script output, with conflicting files kept at their local version.
  2. fix(modules): resolve the v59.2.0 sync conflicts and keep Stellar Engine changes resolves the 72 conflicting files. It starts from upstream and keeps only the local behavior that upstream lacks, as the local changes table in docs/upstream-sync.md lists. It also vendors the dataplex-aspect-types module, which the synced project-factory module calls.
  3. chore(repo)!: raise the Terraform and provider baseline moves default-versions.tf, the styleguide, the documentation, the Stellar Engine modules and the blueprints to Terraform 1.12.2 and the google providers >= 8.6.0, < 9.0.0.
  4. fix(fast)! and fix(blueprints)! adapt every caller to the new module interfaces and to provider 8.
  5. docs(modules) regenerates the README tables of the modules with local changes, using the tools/tfdoc.py script of Fabric v59.2.0.
  6. chore(tools) removes the UPSTREAM_PENDING_SYNC list from the tools/tflint.sh script, because the synced modules now pass the naming rule.
  7. test(cli) makes the preflight tools test read the Terraform floor from the modules instead of hardcoding 1.10.2.
  8. ci(deps) makes the Dependabot coverage test skip manifests in modules that the sync owns, such as the new modules/api-gateway/recipe-multi-region/function/package.json file. Upstream Dependabot updates them, and local updates would conflict with the next sync.

README tooling

These commits fix #319 and get tools/lint.sh passing again.

  1. feat(tools) teaches the sync script to track the repository paths in tools/cff-sync.bases, with the Python formatting step and new shell tests. The tools/cff-sync-pr.sh script commits those paths with the modules, and the weekly workflow sets up uv for the formatting step.
  2. chore(tools) three-way merges tools/tfdoc.py and tools/check_documentation.py from Fabric v35.1.0, the closest upstream ancestor of the local copies, to v59.2.0. The merge keeps the local fixes, which docs/upstream-sync.md lists. The commit also vendors the tests/examples/utils.py directive parser that tools/tfdoc.py imports and all 24 tests/fixtures/ files that module README examples name, and records all four paths in tools/cff-sync.bases.
  3. chore(modules) vendors the net-cloud-armor module, which the synced net-lb-ext README links to.
  4. docs(repo) regenerates the 36 README files that the synced tools/tfdoc.py script reports as stale. Every regenerated synced module README now matches upstream byte for byte, apart from the datafusion-se copy.
  5. ci(security) merges the tests/fixtures/ entry into the Trivy skip-dirs input from ci(security): enforce Trivy SARIF severity filter and suppress false positives #342. An earlier rebase left two skip-dirs keys in the Trivy step, which GitHub Actions rejects as a duplicate key.

Decisions for reviewers

  • The cloud-run-v2-se copy now matches upstream cloud-run-v2 exactly. A follow-up change can point its callers to modules/cloud-run-v2/ and delete the copy.
  • The project module keeps the gcloud step that deletes the default network, because upstream still has no native equivalent.
  • The gke-cluster-standard and gke-cluster-standard-se modules keep the Shielded GKE Nodes default from fix(gke): enable shielded nodes by default and fix gke-hardened feature key #341, because upstream still defaults it to off.
  • The gke-cluster-standard and gke-cluster-autopilot modules keep the public endpoint disabled by default. Upstream removed that default, which would give the fedramp-high/gitlab cluster a public control plane endpoint.
  • The net-vpc callers set directpath = false, because upstream now adds a DirectPath route to every VPC by default.
  • The fedramp-high/gitlab blueprint keeps the authorized range from fix(blueprints): apply fedramp-high/gitlab GKE control plane and node settings #345. The upstream GKE modules now omit master authorized networks when a caller passes no ranges, so every GKE caller in Stellar Engine passes at least one range.
  • The net-lb-ext, net-lb-int and net-lb-proxy-int modules take the upstream v59.2.0 files, which already contain the health check and backend service fixes from fix(modules): fix health check and backend service configs in net-lb-ext, net-lb-int, and net-lb-proxy-int #297.
  • The cnap blueprint lets IAP use a Google-managed OAuth client by default, and the new optional iap_oauth2_client variable accepts a client that operators create in the console. Provider 8 removed google_iap_client after Google shut down the IAP OAuth Admin API.
  • The vertex-mlops blueprint drops the MANAGED notebook type, because Google-managed notebooks reached end of life and provider 8 removed google_notebooks_runtime.
  • The Trivy check reports three npm advisories in the modules/api-gateway/recipe-multi-region/function/package-lock.json file. The file matches upstream v59.2.0 and upstream main byte for byte, so the fix belongs upstream and arrives through the weekly sync.
  • The Trivy misconfiguration scan reports master authorized networks on the upstream GKE module code and IP forwarding on the compute-vm module, which moved from the main.tf file to the instance.tf file upstream. Both alerts depend on caller inputs. The Stellar Engine GKE callers set authorized ranges, and only the stage 2 NVA and NGFW appliances enable IP forwarding, which routing requires and main already reports.
  • The Trivy scan adds the vendored tests/fixtures/ directory to the skip-dirs input from ci(security): enforce Trivy SARIF severity filter and suppress false positives #342, because those files only feed README examples. The tools/tflint.sh script already covers only fast/, blueprints/ and modules/.
  • The datastore and il5/private-service-connect blueprints, the private-service-connect module and the gemini-enterprise blueprints keep their provider ranges. The first three wrap registry modules with their own constraints, and the last ship their own deployment tooling.

Scope

The tooling and the sync land together on purpose, so reviewers see the script with its first real run. The commits keep the tooling separate, so a split into a tooling pull request and a sync pull request stays possible on request.

The README tooling from #319, the vendored test fixtures and the vendored net-cloud-armor module belong here too, because the README and link checks of tools/lint.sh only pass on the synced modules with them. They stay separate commits.

Fixes carried over

The migration surfaced several existing defects. Their fixes merged into main first, and the rebased branch keeps each one on the v59.2.0 interfaces.

The branch also carries recent stage changes from main onto the new module interfaces.

Follow-up work tracks the cleanups that this sync enables.

Breaking Changes

Existing deployments need Terraform 1.12.2, a provider upgrade, and a few state and configuration changes before the first plan. The ! in the title makes Release Please cut a new major release.

Terraform and providers
- Install Terraform 1.12.2 or newer.
- Run `terraform init -upgrade` in every stage and blueprint root, because the
  modules now require the google and google-beta providers >= 8.6.0, < 9.0.0.
- Review the provider 7.0.0 and 8.0.0 upgrade guides for resources that your
  own code declares outside the Stellar Engine modules.

State moves
- moved blocks in the modules, stages and blueprints keep the renamed
  resources, including the secret-manager IAM bindings in stage
  2-networking-b-il5-ngfw and the secret-manager blueprint. Expect plans to
  show moves for them.
- Stage 2-networking-b-il5-ngfw replaces each NGFW SSH key secret version
  once with the same key data, because older state lacks the write-only
  version that the secret-manager module now sets.
- Upstream changed the kms module IAM keys in v53.1.0. Apply twice after the
  upgrade to keep every key binding.

Resources removed by provider 8
- blueprints/fedramp-high/cnap: run
    terraform state rm google_iap_client.project_client
  before the first plan, then delete oauth_brand_number from your tfvars.
  IAP now uses a Google-managed OAuth client, which admits users of your
  organization. Set iap_oauth2_client to a console-created OAuth client to
  admit external users.
- blueprints/fedramp-high/vertex-mlops: run
    terraform state rm 'google_notebooks_runtime.runtime'
  before the first plan, then change notebooks entries with
  type = "MANAGED" to type = "USER_MANAGED" or drop the attribute, and drop
  idle_shutdown. Workbench instances are zonal VMs in your project that run
  as the notebook service account.

Configuration changes
- fast/stages-aw/3-security: ingress and egress policy YAML files under
  data/vpc-sc that list access levels in from.access_levels must write them
  as $access_levels:<name>.
- Forks that call modules directly must follow the interface changes in the
  upstream CHANGELOG.md since v38.0.0, such as the compute-vm, secret-manager,
  net-vpc, vpc-sc, cloud-run-v2 and net-lb-app-ext-regional rewrites, and the
  custom_roles object type in the project and organization modules.
- The alloydb module drops the Stellar Engine primary_read_pools and
  secondary_read_pools variables in favor of the upstream read_pool variable.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

Deployment & Compliance Impact

  • Applicable Regimes:
    • US Region Restricted (e.g., Access Policy constraint)
    • FedRAMP Moderate
    • FedRAMP High
    • DoD IL4
    • DoD IL5
    • General / All
  • NIST 800-53r5 Controls: SI-2 flaw remediation and CM-2 baseline configuration through current upstream modules. The sync keeps the existing CMEK, logging, deletion protection and private endpoint behavior.

Checklist

Code Quality & Reusability

  • My code adheres to the Maximize Reusability principle. I have not redefined common elements and have reused existing base configurations and modules where possible.
  • I have checked that no existing module or configuration in modules/ or fast/stages-aw/ can be leveraged for this change.
  • My code follows the established naming conventions outlined in docs/naming-convention.md.

Documentation

  • I have updated the README.md of the modified module or blueprint.
  • I have added/updated documentation for inputs (variables) and outputs.

Security

  • My change adheres to GCP security best practices and the principle of least privilege.
  • I have ensured compliance with the targeted regime (FedRAMP Moderate, FedRAMP High, IL4, IL5, etc.).

Testing

  • I have tested my changes locally.
  • I have included details of my testing in this PR.

Testing Performed

The checks below ran locally on the branch rebased onto main at e239604. This pull request stays a draft until a test organization confirms the deployment and upgrade paths, which no check here covers.

  • bash tools/run_tests.sh passes with 122 Python tests and the shell suites, including 58 sync script tests and 14 pull request script tests.
  • The cli/ project passes pytest with 969 tests, ruff check, ruff format --check and pyright.
  • bash tools/lint.sh passes 9 of its 10 checks, including terraform fmt -recursive -check, the README check and the link check. The Terraform lint check did not run, because TFLint is not installed locally.
  • tools/tflint.sh with TFLint v0.64.0 passed for all 155 directories, with no skipped modules, before this rebase. The rebase changes only the stage 0 organization.tf file among the Terraform files of the branch.
  • shellcheck 0.11.0 passes for the sync scripts, their tests, tools/tflint.sh and tools/run_tests.sh.
  • zizmor and actionlint report no findings for the ci.yml and cff-sync.yml workflows. Before the ci(security) commit, actionlint reported the duplicate Trivy skip-dirs key.
  • terraform init -backend=false and terraform validate pass for 151 of the 155 Terraform directories under modules/, fast/stages-aw/ and blueprints/. Stages 1 to 3 fail only because the google.billing provider alias has no configuration outside a deployment, which main reports the same way. A local stub for that alias let them validate before this rebase.
  • tools/sync-from-cff.sh --to v59.2.0 --conflict-style ours reported 72 conflicting files, and a dry run on the branch reports no changes for the four tracked paths. Both ran before this rebase, which touches no synced module file.
  • A script compares every module call with the old and new variable types and finds no object attribute that a caller passes and a module no longer declares.
  • Credential-free plans with -refresh=false against main and the branch show the same resources for the 3-security VPC Service Controls perimeter in dry-run and enforced modes, the 2-networking-b bastion, the 2-networking-a NVA templates, and the il5/gke-hardened blueprint, apart from new provider fields such as deletion_policy.
  • A scratch state confirms that terraform state rm removes a google_iap_client entry that provider 8 cannot read, while a removed block cannot.
  • A scratch state confirms that both write-only and plain secret data replace a secret version that the old module wrote, so the upgrade note lists that replacement.
  • A fresh deployment of stages 0 to 3 and a plan of each stage against an existing deployment remain unverified.

@github-actions github-actions Bot added Framework - IL5 DoD Impact Level 5 (IL5) compliance regime and controls Framework - FedRAMP High FedRAMP High compliance regime and controls Scope - Fast Related to Fabric FAST deployment stages in the fast directory Scope - Blueprint Related to solution blueprints in the blueprints directory Scope - Modules labels Oct 20, 2026
@aghassemlouei aghassemlouei added Documentation Improvements or additions to documentation Enhancement New feature or request Priority - Medium Standard features and non-blocking bugs; important for the current milestone but not urgent Level of Effort - High Complex task taking a week or more; consider breaking this down into smaller issues. Scope - Module Related to reusable Terraform modules in the modules directory and removed Scope - Modules labels Oct 20, 2026
@digitalresistor

Copy link
Copy Markdown
Contributor Author

The Trivy failure comes from vendored upstream code, not from changes in this pull request.

All three alerts point at modules/api-gateway/recipe-multi-region/function/package-lock.json, which the sync brings in from Cloud Foundation Fabric. The file matches upstream v59.2.0 and upstream master byte for byte.

Package Locked version Advisory Fixed version Dependency path
proxy-addr 2.0.7 GHSA-jqcg-44mw-7w3h, critical 2.0.8 express → proxy-addr ^2.0.7
fast-uri 3.1.7 GHSA-hrr3-gc8f-f4qj, medium 3.1.8 ajv → fast-uri ^3.0.1
uuid 8.3.2 GHSA-w5hq-g745-h8pq, medium 11.1.1 cloudevents → uuid ^8.3.2
  • A lockfile refresh fixes proxy-addr and fast-uri, because the fixed releases fall inside the existing ranges.
  • uuid needs an npm overrides entry, because the latest cloudevents release still requires uuid ^8.3.2. Upstream Dependabot cannot fix it alone, which is why the April advisory is still open upstream.
  • A local test run confirms the fix: npm audit reports 0 vulnerabilities, cloudevents still loads uuid 11 through require, and the function module loads.

The fix belongs upstream rather than in this branch. A local edit to a vendored file turns into a merge conflict on every weekly sync, and the next sync after the upstream fix brings the corrected lockfile here. The cff-sync.yml workflow is the delivery path.

The recipe is a sample Cloud Function that no stage or blueprint deploys, so the alerts do not affect any deployment. A maintainer can dismiss the three code scanning alerts as vendored code, or leave them open until the sync brings the upstream fix.

@github-advanced-security github-advanced-security AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Trivy found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

@digitalresistor

Copy link
Copy Markdown
Contributor Author

Rebased onto main at 80b7d4a, after #286, #291, #284, #338, #339, #340 and #336. The branch keeps its 11 commits and their messages, and the previous head stays on the backup/sync-cff-v59-v3 branch.

Conflict resolutions

Verification

  • terraform init -backend=false and terraform validate pass for all 104 module directories and all 48 roots under fast/stages-aw/ and blueprints/, with Terraform 1.13.3 and google provider 8.8.0. Stages 1 to 3 use a temporary billing alias stub for both google providers.
  • bash tools/run_tests.sh passes, with 100 Python tests and the shell suites, including 43 sync script tests and 10 pull request script tests.
  • uv run --project cli pytest cli/tests passes 160 tests.
  • tools/tflint.sh with TFLint v0.64.0 passes for all 152 directories.
  • bash tools/lint.sh passes 8 of its 10 checks and fails the README and link checks.
  • The README check fails for 87 README files, all in modules that the sync owns. The local tools/tfdoc.py script renders object types with a title tooltip, and the Fabric v59.2.0 tfdoc omits it.
  • The link check fails for 35 links in 11 synced README files. They point to upstream tests/fixtures/ files and to the net-cloud-armor module, which Stellar Engine does not vendor.
  • Both checks already failed before this rebase. The old tools/tfdoc.py stopped on the first unknown fixture, and tools/lint.sh exited 0 on failures. Since chore(repo): fix repo-wide lint failures and make tools/lint.sh fail closed #286, tools/lint.sh fails closed and CI runs it, so the repo-lint job fails on this branch until the README tooling follows upstream. [Feature Request] Sync the repository tooling under tools/ from upstream Cloud Foundation Fabric #319 tracks that sync of tools/.
  • git range-diff shows commits 3, 4, 6, 7 and 8 changed and the other 6 unchanged. Only the sync and resolve commits differ in their file lists, and the final tree differs from the previous branch only in files that main changed.

Open items

The branch stays a draft until a test organization confirms a fresh deployment and an upgrade plan.

The sync adds modules/api-gateway/recipe-multi-region/function/package.json,
which the Dependabot coverage test rejects. Upstream Dependabot already
updates that manifest, and local updates would conflict with the next
sync, so the test skips manifests in modules whose versions.tf file
records a Fabric release.
The tools/sync-from-cff.sh script now also syncs the repository paths
that the tools/cff-sync.bases file lists with a slash in the first field,
as "<local path> <upstream path> <base release>". An entry is either a
directory or a single file, and it gets the same three-way merge, base
tracking and report rows as a module. The --modules option accepts these
paths too, and the dirty-tree guard covers them.

Python files outside modules/ follow the repository ruff format style
while upstream uses 2-space indents. The script formats the base and the
target blob with ruff before it compares and merges them, so only real
upstream changes reach the local copy. A path that upstream left alone
skips the formatting. The CFF_SYNC_PY_FORMAT variable overrides the
formatter, which the tests use to stay hermetic, and the cff-sync.yml
workflow now sets up uv for the default formatter.

The tools/cff-sync-pr.sh script stages the tracked paths with the
modules, so a release that changes only the tooling still opens a pull
request, and its title and body name modules and tooling.

The report and console output now print the full local path of each
conflicting file instead of rebuilding it from the module name.
…59.2.0

The tools/tfdoc.py and tools/check_documentation.py scripts predated the
vendored modules, so regenerating a synced README rewrote every table and
the README check failed on 87 synced modules.

- Three-way merge both scripts from Fabric v35.1.0, the closest upstream
  ancestor of the local copies, to v59.2.0, with both upstream sides in
  the repository ruff format style. The merge keeps the local fixes: the
  ruff style and lint fixes, missing parser contexts, non-greedy README
  markers, escaped pipes in output descriptions, the named failure labels
  and the checks that only run on READMEs with tables.
- Drop the local tftest regular expression and the fallback for missing
  fixtures in favor of the upstream directive parser. Vendor the
  tests/examples/utils.py parser module, which the tfdoc.py script
  imports, in the repository Python style.
- Vendor all 24 files under the tests/fixtures/ directory, which module
  README examples name and the tfdoc.py script links. The script now
  fails on an unknown fixture again, as upstream does.
- Track the four paths in the tools/cff-sync.bases file at v59.2.0, so
  the weekly sync keeps them current, and list their local changes in the
  docs/upstream-sync.md guide.
- Skip the tests/fixtures/ directory in the Trivy scan, because the
  fixtures only feed README examples. The tools/tflint.sh script already
  covers only fast/, blueprints/ and modules/.
- Replace the tfdoc tests for the dropped expression with tests for the
  directive parser and the fixture links.

Fixes google#319.
The synced modules/net-lb-ext/README.md file links to the net-cloud-armor
module, which Stellar Engine did not vendor, so the link check failed.
Vendoring the modules/net-cloud-armor/ module fixes the links, and the
weekly sync keeps it current through the module_name in its versions.tf
file. The OpenTofu versions.tofu file stays out, as the
tools/cff-sync.ignore file requires.
Regenerate the 36 README files that the v59.2.0 tools/tfdoc.py script
reports as stale. Variable tables drop the type tooltips that the old
script rendered and upstream never renders, fixture lists link to the
vendored tests/fixtures/ directory, and the modules/project-factory/
README drops its Contents TOC entry. Every regenerated synced module
README now matches upstream v59.2.0 byte for byte, except the
modules/datafusion-se/ copy.
@github-actions github-actions Bot added Security Something is insecure or can be secured Dependencies - JavaScript Pull requests that update JavaScript and npm dependencies Bug Something isn't working Framework - FedRAMP Moderate FedRAMP Moderate compliance regime and controls Framework - IL4 DoD Impact Level 4 (IL4) compliance regime and controls labels Nov 2, 2026
The rebase onto the Trivy severity filter from google#342 left two skip-dirs
keys in the Trivy step of the ci.yml workflow. GitHub Actions rejects a
workflow with a duplicate key, so the step lists the recipe directories
from google#342 and the vendored tests/fixtures/ directory in one skip-dirs
input.
Comment thread modules/gcs/iam.tf Fixed
@Calvin-Cheng1
Calvin-Cheng1 marked this pull request as ready for review November 9, 2026 15:45
@Calvin-Cheng1 Calvin-Cheng1 changed the title feat(modules)!: sync Cloud Foundation Fabric modules to v59.2.0 and add sync tooling feat(modules)!: sync Cloud Foundation Fabric modules to v60 and add sync tooling Nov 9, 2026
@Calvin-Cheng1 Calvin-Cheng1 changed the title feat(modules)!: sync Cloud Foundation Fabric modules to v60 and add sync tooling feat(modules)!: sync Cloud Foundation Fabric modules to v60.0.0 and add sync tooling Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug Something isn't working Dependencies - JavaScript Pull requests that update JavaScript and npm dependencies Documentation Improvements or additions to documentation Enhancement New feature or request Framework - FedRAMP High FedRAMP High compliance regime and controls Framework - FedRAMP Moderate FedRAMP Moderate compliance regime and controls Framework - IL4 DoD Impact Level 4 (IL4) compliance regime and controls Framework - IL5 DoD Impact Level 5 (IL5) compliance regime and controls Level of Effort - High Complex task taking a week or more; consider breaking this down into smaller issues. Priority - Medium Standard features and non-blocking bugs; important for the current milestone but not urgent Scope - Blueprint Related to solution blueprints in the blueprints directory Scope - Fast Related to Fabric FAST deployment stages in the fast directory Scope - Module Related to reusable Terraform modules in the modules directory Security Something is insecure or can be secured

Projects

None yet

4 participants