Skip to content

Conversation

@robholland
Copy link
Contributor

What was changed

Switched recipes to use envconfig.

Why?

This demonstrates the new envconfig feature and makes it easy for people to switch between local and cloud development.

Checklist

  1. Closes [Feature Request] Support deployment of recipes to both local dev and Temporal Cloud. #7

  2. How was this tested:
    Manually tested locally and then against cloud by following the updated README instructions.

export TEMPORAL_PROFILE=cloud
```

2. Configure the cloud profile using the Temporal CLI:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might want to add a very brief statement on how one can confirm that an envconfig profile is properly configured. Something like this, after the config commands:

To confirm that the profile is working properly, you may run:

  temporal workflow count

This relies on the TEMPORAL_PROFILE env variable already set before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature Request] Support deployment of recipes to both local dev and Temporal Cloud.

3 participants