Skip to main content

CI/CD

NetActuate infrastructure can be provisioned and managed as part of your CI/CD pipeline. Whether you are deploying application code to existing servers or spinning up new infrastructure on every release, the NetActuate API and IaC tools integrate into standard pipeline workflows.

Common CI/CD Patterns​

Deploying to Existing Infrastructure​

The most common pattern is deploying application code to VMs that already exist. Your pipeline SSHes into your NetActuate servers and runs deployment commands — no different from deploying to any other cloud provider.

Provisioning Infrastructure in a Pipeline​

For ephemeral or environment-per-branch workflows, you can provision NetActuate resources as a pipeline step:

  • Terraform / OpenTofu — run terraform apply in your pipeline to create servers, then terraform destroy to tear them down. See Terraform Automation.
  • Ansible — run playbooks to provision and configure servers as part of your deployment. See Ansible Automation.
  • API calls — use curl or an SDK to call the NetActuate API directly from your pipeline scripts.

API Token Management​

Store your NetActuate API key as a secret in your CI/CD platform (GitHub Actions secrets, GitLab CI variables, Jenkins credentials, etc.) and reference it as an environment variable:

# GitHub Actions example
env:
  NETACTUATE_API_KEY: ${{ secrets.NETACTUATE_API_KEY }}

Note: Never commit API keys to your repository. Use your CI/CD platform's secrets management to inject credentials at runtime.

Works With Any CI/CD Platform​

Because NetActuate resources are managed via a standard REST API, they work with any pipeline tool — GitHub Actions, GitLab CI, Jenkins, CircleCI, Buildkite, Argo, or anything else that can make HTTP requests or run CLI tools.

Need Help?​

Contact support@netactuate.com or visit the support page.