Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Will <https://docs.prefect.io/orchestration/concepts/automations.html|Automations> only be available on Prefect Cloud (not server)? Seems that way, but this documentation page doesn't display the blue "cloud" label that the other cloud-only features (like KV Store) have.

<@ULVA73B9P> open “Add Cloud Only label to Automations Page in Docs”

<https://github.com/PrefectHQ/prefect/issues/4978>

Thanks for flagging <@U01KS871YAU>, yes it will only be available on Cloud unfortunately. There are some services needed for this that only Cloud has

Thanks for clarifying. Would it be safe for us to continue using <https://docs.prefect.io/orchestration/concepts/cloud_hooks.html|Cloud Hooks> instead? That page has an italicized note at the top making it sound like a deprecated feature.

Yes we likely won’t remove them, but at the same time, we’re unlikely to add new functionality also

One question on the same topic as well :slightly_smiling_face: Is it possible to configure the host of the `Link` in the response of the Slack message? Currently the one we get is not setting our prefect server URL.
Example message in Slack:
```Run perky-hippo of flow Cloud Hook Test Flow entered a new state:
State: Success
Message: Test success state
Link: <http://prefect-hasura.prefect:3000/v1alpha1/graphql/test-slug/flow-run/>&lt;run-id&gt;```
As you see, `prefect-hasura.prefect` is probably Cloud host.. This is the test request, but the same happens for the Success/Failure/etc. ones

Hi <@U01SQUQC086> the "link" should be using the config value of `server_config.api.url` - the default value is here <https://github.com/PrefectHQ/server/blob/master/src/prefect_server/config.toml#L24>, and you can override in your custom` config.toml`

Is the host in the link not matching your `api.url` configuration?

Hi <@U01SRTRJC0Y> :slightly_smiling_face: Thanks for the answer! I see now.. Our apollo service is in k8s and this is using the name/url of the service in k8s. And this is not available outside of the cluster…

We are using helm chart to set it up. This `api.url` value is overriden by `PREFECT_API_URL` env var, right?

Actually, this value is in this env var: `PREFECT_SERVER__API__URL`

Is this used only for this (cloud hooks), or there are other usages for it? And if it’s only for this, can we configure this in helm chart? Thanks! :slightly_smiling_face:

Ok, it looks like it can be overriden here: <https://github.com/PrefectHQ/server/blob/673cbeab144cb2ae06a17c23fdfb4e2356f0376c/helm/prefect-server/values.yaml#L106>. I’m only interested now it this affect anything else. Thanks!

The default value is defined <https://github.com/PrefectHQ/server/blob/673cbeab144cb2ae06a17c23fdfb4e2356f0376c/helm/prefect-server/templates/_helpers.tpl#L184|here> btw…

A nice you're way ahead of me on the Helm chart configuration! A quick search through the codebase doesnt turn up any other uses in Python.

However, I'd expect the url in general to control which path is used for Hasura. I'm not sure if there would be adverse affects to modifying this variable as a result.

Hah, thanks :smile: I saw this `PREFECT_SERVER__API__URL`is set up in graphql pod as well, so I guess changing this everywhere would probably bring some issues…