aevatar-service-publisher

To publish an Aevatar workflow as a REST API service, you convert the workflow into an invocable service and register it securely using NyxID. This handles the service lifecycle from revision to deploy, making it externally accessible.

NyxID integration is used for secure service registration and invocation when publishing Aevatar artifacts. It ensures published members, teams, or workflows have secure access controls during external REST API triggering.

Yes, you need both Aevatar and NyxID service connections to manage the service lifecycle. These dependencies are required to handle revisions, deployments, rollouts, and secure REST API invocations effectively.

Yes, you can convert Aevatar members and teams into callable services. The publishing process transforms these artifacts into invocable endpoints registered with NyxID for secure REST API access and management.

The best way to manage service revisions and rollouts for published workflows is using an automated service lifecycle approach. This handles publishing, deploying, and rolling out updates while maintaining secure NyxID registration.

Publishing a workflow as a service requires NyxID to provide secure service registration and invocation. It acts as the security layer ensuring REST API calls to the published Aevatar artifacts are properly authenticated.