Organizing Pulumi project

Within your Pulumi project, there are good practices to consider to help keep your code organized, maintainable, and understandable.

Organize your code in a way that makes it easy to understand and maintain. One way to do this in Typescript is to break out your code into separate files, and then import them into your main file.

This project looks a bit like this:

├─ pulumi-ask-workshop
  ├── resources
    ├── akscluster.ts
    ├── certmanager.ts
    ├── containerregistry.ts
    ├── namespaces.ts
    ├── nginxingresscontroller.ts
    ├── virtualnetwork.ts
  ├── config.ts
  ├── index.ts
  ├── package-lock.json
  ├── package.json
  ├── Pulumi.yaml
  ├── Pulumi.dev.yaml
  ├── tsconfig.json

Let’s discuss them briefly:

• resources — all the azure resources for provisioning your system on azure

• config.ts — get all configurations from Pulumi

• index.ts— is the Pulumi program that defines your stack resources.

• package.json and package-lock.json—definitions of required npm dependencies

• Pulumi.yaml and Pulumi.dev.yaml—contains configuration values for the stack you initialized.

• tsconfig.json—settings for the TypeScript compiler

• .gitignore—Git exclusion list, is not important for us

• node_modules—installed npm packages

Now that we have our folder structure, we can create all the resources that the service needs.