Skip to content

docs: add blog post on local PAC dev environment#714

Open
theakshaypant wants to merge 1 commit intotektoncd:mainfrom
theakshaypant:pac-local-dev
Open

docs: add blog post on local PAC dev environment#714
theakshaypant wants to merge 1 commit intotektoncd:mainfrom
theakshaypant:pac-local-dev

Conversation

@theakshaypant
Copy link
Copy Markdown
Member

Changes

Add a guide for setting up a local Pipelines-as-Code development environment using the startpaac tool. Covers prerequisites, installation, GitHub App configuration, and a first pipeline run walkthrough.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide
for more details.

Add a guide for setting up a local Pipelines-as-Code development
environment using the startpaac tool. Covers prerequisites,
installation, GitHub App configuration, and a first pipeline run
walkthrough.

Signed-off-by: Akshay Pant <[email protected]>
@tekton-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign twogiants after the PR has been reviewed.
You can assign the PR to them by writing /assign @twogiants in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Mar 28, 2026
ko >= 0.14

# CLI utilities
gum >= 0.11
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

i made gum optional here fyi pipelines-as-code/startpaac#21

Copy link
Copy Markdown
Member

@chmouel chmouel left a comment

Choose a reason for hiding this comment

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

I think it's good but startpaac is more tailored for local devs than end user getting started, end users should probably do https://pipelinesascode.com/docs/getting-started/

# CLI utilities
gum >= 0.11
jq >= 1.6
minica
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

maybe ad some links

- Tekton Triggers for advanced event handling
- Tekton Chains for supply chain security
- PostgreSQL database
- GitHub Second Controller for enterprise setups
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

for multiple multiple controller testing (ie: second github enterprise instance)

- Contribute features back to the PAC project
- Experiment with unreleased PAC functionality

## GitHub Integration Setup
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

i think you can just give tkn pac bootstrap --skip-install

2. Generate a **private key** and download it
3. Install the app on your test repository

#### 4. Set Up Webhook Forwarding
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

tkn pac bootstrap would do it..


#### 5. Create Secret Files

Create the secret files that startpaac expects:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

with tkn pac bootstrap you just need to dump the secrets yaml to the disc, we can add an option to startpaac to instead read from a folder, read from a yaml which is the same as what we have on cluster..

@theakshaypant
Copy link
Copy Markdown
Member Author

I think it's good but startpaac is more tailored for local devs than end user getting started, end users should probably do https://pipelinesascode.com/docs/getting-started/

Yes, this is in now way a guide to run PAC locally but targeted for anyone who wants to setup a dev environment, as the title also suggests "Setting Up a Local Pipelines-as-Code Development Environment".
Will work on the suggested changes if you think this would be a helpful addition to the website, we can close it otherwise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants