Open divyenduz opened 6 years ago
I've tried to deploy it again. Still not working.
Can confirm this issue on a version 1.32 server. Deployment works, but service is not picked up by Prisma-cloud. I had a service on the default endpointdefault/default
and i created antoher service onsomeOtherName/default
. The service is also accessible via prisma admin
, but not via the cloud interface, there's no service appearing on the dropdown:
I tried refreshing and i have also redeployed.
We're running our self-hosted server in version 1.32.2 on the AWS Fargate stack.
Workaround:
yanr prisma admin
or
yarn prisma admin -e .env.prod
if yo have your prod env in a file.
I am facing the same problem. Service is deployed but is not showing up under Services in my workspace. This is very annoying :S
update:
solved with prisma delete -e dev.env
and deploy again prisma deploy -e dev.env
now I can see the service in the Services tab
Currently, Prisma cloud is made aware of service when we do Prisma deploy. If there is an outage that fails this workflow and the service is deployed. That yields a state where the service is live and deployable but not visible in console.
A script can be created to sync the services from all the servers added to workspace periodically.
Current work around is to deploy the service again and it will be visible in Prisma cloud.