Feature ideas

Currently defining an input as a secret does not work in cases where there is an approver on the action. https://docs.getport.io/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/secret Port should support using input secrets and approvers in the same action.

For some actions, I would like to be able to display or not some steps. For example, I would like a step for selecting an entity if it exist, or display a step to create it if it is not exists already.

In some cases an operation failed and a retry will solve it. Adding a retry action for a run can be nice addition :)

It's nice to have some log stream formatting options. I like the approach Azure Devops uses. Could you implement something like this: https://learn.microsoft.com/en-us/azure/devops/pipelines/scripts/logging-commands?view=azure-devops&tabs=bash Not sure if GitHub actions or Jenkins have something similar, to cover several CI/CD systems in a one shot, and highlight log lines automatically. Additionally, to this, it's nice to have some console auto colouring support, like on the TF plan screenshot:

As self service action URL do now exists: https://app.getport.io/self-serve?action=my-action . It will be great if we can add also pre-filled form parameter to the URL, something that could looks like this: https://app.getport.io/self-serve?action=my-action&key1=value1&key2=value2

Basically, add Codefresh here: https://docs.getport.io/create-self-service-experiences/setup-backend/ More specifically, the Action in Port should be able to trigger a Classic Codefresh Pipeline ( link ), not to be confused with an Argo Workflows|Events pipeline.

Allow developers to upload or insert various configuration file types (e.g., .py, .conf, .txt) directly into the self service action form for "creating a microservice", for example. This feature should support a range of file formats beyond the current YAML, JSON, and Protobuf, and offer the option of markdown/free text input for added flexibility. Here is an example of a microservice file structure: Microservice/ │ │── MS-code/ │── values-files/ │ │ ├── production.yaml | | ├── staging.yaml │ │ └── testing.yaml │ │ │ └── configmaps/ │ ├── prod | | ├── settings.yaml |. | ├── gunicorn.py |. | └── nginx.conf | ├── stage | | ├── settings.yaml |. | ├── gunicorn.py |. | └── nginx.conf │ └── test | ├── settings.yaml |. ├── gunicorn.py |. └── nginx.conf │ │ └── README.md

We have a few places today where we are attempting to link to a specific self-service action, and have had success using a relative URL like /self-serve?action=[action.identifier] . As an example, we have the following action today: action identifier : create_dbt_repo action inputs : team_name ( enum ), app_name ( string ) It would be nice to be able to default one or more values in the self-service action user input form (on a per instance basis) with a URL like: /self-serve?action=create_dbt_repo&app_name=test . (Note: This is different than defaulting the field at the form level - if someone comes in and manually triggers this action, I don't want to default anything for app_name - but in cases where we are linking to the action from specific pages elsewhere, it would be nice to use the information known at that point to drive some context-specific defaults when they arrive on the self-service action form.)

On catalog pages there is an action icon (lightning bolt) next to entities that lets you invoke actions directly from the table. Currently you have to click twice, once to open the list and once to select the action. It would be nice to remove a click by displaying the action list when hovering over the icon.

Add the ability to dynamically decide whether the self-service action will have an approval step or not. How it will work - upon the action execution, a webhook can be sent to the customer's backend in order to run a logic that will decide if this specific action run needs to be approved by someone before executed