A
Ayodeji Adeoti
As an example: I have different GH actions configured for provisioning resources on AWS depending on the resource requested:
  • Action A: To provision an EC2 instance
  • Action B: To provision an S3 bucket
  • Action C: To provision an AWS user
  • Action D: To provision a lambda function
  • Action E: To provision a Postgres DB
I have a single SSA, "Provision AWS Resource" which contains several advanced inputs which are visible or disappear based on the resource type selected. Due to Port's current setup, I have to combine these 5 GH actions into one since the SSA can only trigger one backend. This will cause my GH action to be huge, convoluted and complex, when I could just configure my SSA to send a payload to a backend (GH action A - E) depending on the resource to be provisioned.
Also, I should be able to configure the format of the payload per backend. This allows a single generic SSA but different branches of GH actions (or a different backend pipeline) to be used for complex use cases.