Skip to content

chore: Added docs section on env vars in yaml #2792

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
feast-ci-bot merged 3 commits into from
Jun 15, 2022
Merged

chore: Added docs section on env vars in yaml #2792

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ace2817
Added Spark support for Delta and Avro
creativedutchmen Jun 4, 2022
2ba4e2e
Added a section about using env variables in the yaml config
creativedutchmen Jun 14, 2022
aea5b0e
Added info on adding defaults when using env var in yaml
creativedutchmen Jun 15, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions docs/how-to-guides/running-feast-in-production.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -310,6 +310,30 @@ We use an [InfluxDB-style extension](https://github.com/prometheus/statsd_export
We chose StatsD since it's a de-facto standard with various implementations (eg, [1](https://github.com/prometheus/statsd_exporter), [2](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/statsd/README.md))
and metrics can be easily exported to Prometheus, InfluxDB, AWS CloudWatch, etc.

## 7. Using environment variables in your yaml configuration

You might want to dynamically set parts of your configuration from your environment. For instance to deploy Feast to production and development with the same configuration, but a different server. Or to inject secrets without exposing them in your git repo. To do this, it is possible to use the `${ENV_VAR}` syntax in your `feature_store.yaml` file. For instance:

```yaml
project: my_project
registry: data/registry.db
provider: local
online_store:
type: redis
connection_string: ${REDIS_CONNECTION_STRING}
```

It is possible to set a default value if the environment variable is not set, with `${ENV_VAR:"default"}`. For instance:

```yaml
project: my_project
registry: data/registry.db
provider: local
online_store:
type: redis
connection_string: ${REDIS_CONNECTION_STRING:"0.0.0.0:6379"}
```

---
## Summary

Expand Down
2 changes: 2 additions & 0 deletions sdk/python/feast/infra/offline_stores/contrib/spark_offline_store/spark_source.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,8 @@ class SparkSourceFormat(Enum):
csv = "csv"
json = "json"
parquet = "parquet"
delta = "delta"
avro = "avro"


class SparkSource(DataSource):
Expand Down