Pulumi is an open source infrastructure-as-code software
tool you can use to create, deploy, and manage infrastructure on any cloud in the
language of your choosing.
Palo Alto Networks Cortex XCOR provides a
Pulumi package
for managing Cortex XCOR resources. See
Supported resources for a list
of supported resources.
Use Cortex XCOR and Pulumi together to provide a seamless process to
manage and monitor Kubernetes workloads. When you deploy Kubernetes resources using
Pulumi, you can use Cortex XCOR to monitor those resources in real time.
Codify your infrastructure using Pulumi, and gain observability using Cortex XCOR.
Getting started
Complete the following steps to get started with the Cortex XCOR Pulumi provider.
- Install the provider.
- Configure environment variables.
Install
To use the Cortex XCOR Pulumi provider, install the Pulumi provider for your
preferred language.
After installing the Cortex XCOR Pulumi provider, configure environment variables to
authenticate with Cortex XCOR and manage resources in your tenant.
API token
Pulumi performs tasks that require administrative privileges, and requires an API
token with administrative privileges to authenticate. Use either an unrestricted
service account, or a user or service account that belongs to a team with the
SysAdmin role.
To authenticate as a service account, use the API token generated and provided upon
account creation. For details, see service accounts.
To authenticate as an administrative user account, use a
personal access token.
If you don’t provide a token as an argument, Pulumi then looks for it in the
environment variable CHRONOSPHERE_API_TOKEN, which you can set by running the
following command or adding it to your shell profile:
Replace
API_TOKEN with the API token generated from your
service account. Cortex XCOR recommends storing your API token in a separate file or Kubernetes Secret and calling it using an environment variable, such as
$API_TOKEN.
Organization name
Pulumi needs the name of your team’s organization as the --org-name argument. If
you don’t provide your organization’s name as an argument, Pulumi looks for it in the
environment variable CHRONOSPHERE_ORG_NAME.
To set this variable, run the following command or add it to your shell profile:
Replace SUBDOMAIN_NAME with the subdomain name you use to access Cortex XCOR. For example,
if your team uses example.chronosphere.io, your team’s organization name is
example.
Resources
Refer to the Cortex XCOR Pulumi provider
API docs for a
list of resources you can create and manage with the provider.