Skip to content

Commit 4731a41

Browse files
authored
Merge branch 'main' into update-apiSpec-20-10
2 parents 3962f5f + 498ea1e commit 4731a41

File tree

121 files changed

+2259
-1115
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

121 files changed

+2259
-1115
lines changed

.github/workflows/verify-docs-build.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ jobs:
2222
with:
2323
persist-credentials: true
2424
- name: Install dependencies
25-
uses: actions/setup-node@v5
25+
uses: actions/setup-node@v6
2626
with:
2727
node-version: lts/*
2828
cache: npm

docs/actions-and-automations/actions-and-automations.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,12 @@ import PortTooltip from "/src/components/tooltip/tooltip.jsx"
55
One of Port's core offerings is the ability to automate and simplify the processes and routines of your developers.
66
This is done using two powerful tools:
77

8-
## 1. Self-service actions
8+
## 1. Actions
99

10-
Create a wide range of personalized, controlled actions that developers can use to scaffold a service, provision a cloud resource, or any other logic that serves your organization.
11-
Self-service actions drive developer productivity by providing a consistent and repeatable way to perform common tasks, all with guardrails like manual approvals or consumption policies to comply with organizational standards.
10+
Actions are executable pieces of logic that developers or AI agents can run. You can create a wide range of personalized, controlled actions to scaffold a service, provision a cloud resource, or any other logic that serves your organization. Actions drive developer productivity by providing a consistent and repeatable way to perform common tasks, all with guardrails like manual approvals or consumption policies to comply with organizational standards.
1211

1312
:::tip Live demo
14-
For real-world examples of self-service actions, check out our [live demo](https://demo.getport.io/self-serve).
13+
For real-world examples of self-service actions, check out our [live demo](https://showcase.port.io/self-serve).
1514
:::
1615

1716
For more information and instructions for creating self-service actions, click [here](/actions-and-automations/create-self-service-experiences).
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
{
2-
"label": "Create self-service actions",
2+
"label": "Create actions",
33
"position": 1
44
}

docs/actions-and-automations/create-self-service-experiences/create-self-service-experiences.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,9 @@ import ExecuteActionLocations from '/docs/actions-and-automations/create-self-se
1414
</center>
1515
<br/>
1616

17-
Drive developer productivity by allowing developers to use self-service actions like scaffolding a service or provisioning a cloud resource. Developer self-service drives consistency and repeatability and ensures that their routines are intuitive and clear, all with guardrails like manual approvals or consumption policies to comply with organizational standards.
17+
Actions are executable pieces of logic that either developers or AI agents can run. They drive developer productivity by enabling them to use actions like scaffolding a service or provisioning a cloud resource.
18+
19+
Actions drive consistency and repeatability and ensure that routines are intuitive and clear, all with guardrails like manual approvals or consumption policies to comply with organizational standards.
1820

1921
Port's action model is designed to be flexible and can be used to cover a wide range of use-cases:
2022

@@ -24,7 +26,7 @@ Port's action model is designed to be flexible and can be used to cover a wide r
2426
4. **Stateful** - every invoked action affects the software catalog by adding/modifying/deleting one or more entities.
2527
5. **Secure by design** - does not require keys to sensitive infrastructure by using an event-based model. All actions are audited and can include guardrails like manual approval and TTL.
2628

27-
## 💡 Common self-service actions
29+
## Common self-service actions
2830

2931
- [**Scaffold** a new service](https://docs.port.io/guides/all/scaffold-a-new-service/).
3032
- [**Create** a cloud resource](https://docs.port.io/guides/all/create-cloud-resource-using-iac).
@@ -33,11 +35,11 @@ Port's action model is designed to be flexible and can be used to cover a wide r
3335
- **Rollback** a running service.
3436
- **Change** a deployment's replica count.
3537

36-
In our [live demo](https://demo.getport.io/self-serve), you can see examples for self-service experiences. 🎬
38+
In our [live demo](https://showcase.port.io/self-serve), you can see examples for self-service experiences. 🎬
3739

3840
## How does it work?
3941

40-
1. A user **executes an action** from Port's UI interface.
42+
1. A user or AI agent **executes an action** from Port's UI interface or through API calls.
4143
2. A pre-defined **payload** containing any desired metadata about the action and its inputs is **sent** to your infrastructure.
4244
3. A **job is triggered** and the user gets a **continuous indication** about its progress.
4345
4. Once the action is running, you can use Port's API to **update Port on its status** and provide information such as **logs and links to the resulting handlers**.

docs/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/entity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ The entity input type can be used to reference any existing entity from the soft
2121
- Clusters
2222
- Configurations
2323

24-
In the [live demo](https://demo.getport.io/self-serve) self-service hub page, we can see the **scaffold new service** action whose `Domain` input is an entity input. 🎬
24+
In the [live demo](https://showcase.port.io/self-serve) self-service hub page, we can see the **scaffold new service** action whose `Domain` input is an entity input. 🎬
2525

2626
## Sorting entities
2727

docs/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/number.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ The number input type can be used to store any numeric data, for example:
2121
- Replica counts
2222
- Number of days to retain data
2323

24-
In the [live demo](https://demo.getport.io/self-serve) self-service hub page, we can see the **scaffold new service** action whose `K8s Replica Count` input is a number input. 🎬
24+
In the [live demo](https://showcase.port.io/self-serve) self-service hub page, we can see the **scaffold new service** action whose `K8s Replica Count` input is a number input. 🎬
2525

2626
## API definition
2727

docs/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/object.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The object input type can be used to store any key/value based data, for example
2222
- HTTP responses
2323
- Dictionaries/Hash maps
2424

25-
In the [live demo](https://demo.getport.io/self-serve) self-service hub page, we can see the **Open terraform PR to add S3 bucket** action whose `policy` input is an object input. 🎬
25+
In the [live demo](https://showcase.port.io/self-serve) self-service hub page, we can see the **Open terraform PR to add S3 bucket** action whose `policy` input is an object input. 🎬
2626

2727
## API definition
2828

docs/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/team.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ The team input type can be used to reference any team that exists in Port, for e
2121
- The current on-call
2222
- The lead maintainers
2323

24-
In the [live demo](https://demo.getport.io/self-serve) self-service hub page, we can see the **scaffold new service** action whose `Owning Team` input is a user input. 🎬
24+
In the [live demo](https://showcase.port.io/self-serve) self-service hub page, we can see the **scaffold new service** action whose `Owning Team` input is a user input. 🎬
2525

2626
## API definition
2727

docs/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/text.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The text input type can be used to store any text based data, for example:
2222
- Commit SHA
2323
- File names
2424

25-
In the [live demo](https://demo.getport.io/self-serve) self-service hub page, we can see the **scaffold new service** action whose `Service Name` input is a text input. 🎬
25+
In the [live demo](https://showcase.port.io/self-serve) self-service hub page, we can see the **scaffold new service** action whose `Service Name` input is a text input. 🎬
2626

2727
## API definition
2828

docs/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/toggle.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ This input type can be used to store any true/false gate, for example:
2323
- Does service handle PII
2424
- Is environment public
2525

26-
In the [live demo](https://demo.getport.io/self-serve) self-service hub page, we can see the **Delete Repo** action whose `Confirm` input is a toggle input. 🎬
26+
In the [live demo](https://showcase.port.io/self-serve) self-service hub page, we can see the **Delete Repo** action whose `Confirm` input is a toggle input. 🎬
2727

2828
## API definition
2929

0 commit comments

Comments
 (0)