ArgoCD repo url
In the ArgoCD ocean integration's default blueprints this field is defined with type Url. In fact, it can have several formats which don't fit the formatting requirements for Url (including git@ and ssh://)
Edit the AWS exporter in Port
Currently, the AWS exporter's mapping is saved inside a config.json in a dedicated S3 bucket. This method makes changing the mapping difficult because it requires changing the config.json and rerunning the integration. Instead, we are planning to allow users to change the AWS exporter's mapping right from Port (similar to other integrations). After the update, the AWS exporter will automatically resync according to the new mapping.
Display ocean logs in the UI
To make the investigations of Ocean integration issues more easy, we will display the recent logs of each ocean integration in the "Data source" page
Edit the Kubernetes exporter in Port
Currently, the K8s exporter's mapping is saved inside a config.yaml in the Cluster. This method makes changing the mapping difficult because it requires changing the config.yaml and then rollout the change. Instead, we are planning to allow users to change the K8s exporter's mapping right from Port (similar to other integrations). After the update, the K8s exporter will automatically resync according to the new mapping.
Add Codefresh as a supported Backend for an Action triggered from Port
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.
Adding mapping config to helm charts
Currently, you can update the integration mapping config and default blueprints through the ocean integration after deploying. Adding the option to provide those as parameters in the helm chart could make the process of deploying integrations faster and better.
Slack ChatOps Bot
Developers should be able to perform self-service actions from within Slack (or other Chat platforms like MS Teams), as well as retrieve data about the system.
Azure DevOps Repositories support
An integration with Azure DevOps Repositories would provide features and capabilities similar to what we provide today with our GitHub, GitLab and Bitbucket integrations. The integration will make it possible to use an app-config to export information from Azure DevOps Repositories to Port and keep them up to date in real time. The integration will make it possible to report entities and properties from Azure DevOps Repositories using GitOps via a port.yml file.