Skip to content

Commit 89bc551

Browse files
tokokotokoko
authored
chore: Remove serverless feature server deployments (feast-dev#4272)
1 parent b4d54af commit 89bc551

24 files changed

Lines changed: 13 additions & 784 deletions

File tree

‎.github/workflows/master_only.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ jobs:
9494
runs-on: ubuntu-latest
9595
strategy:
9696
matrix:
97-
component: [ feature-server-python-aws, feature-server-java, feature-transformation-server ]
97+
component: [ feature-server-java, feature-transformation-server ]
9898
env:
9999
MAVEN_CACHE: gs://feast-templocation-kf-feast/.m2.2020-08-19.tar
100100
REGISTRY: gcr.io/kf-feast

‎Makefile‎

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -397,14 +397,6 @@ build-feature-server-docker:
397397
-t $(REGISTRY)/feature-server:$$VERSION \
398398
-f sdk/python/feast/infra/feature_servers/multicloud/Dockerfile --load .
399399

400-
push-feature-server-python-aws-docker:
401-
docker push $(REGISTRY)/feature-server-python-aws:$$VERSION
402-
403-
build-feature-server-python-aws-docker:
404-
docker buildx build --build-arg VERSION=$$VERSION \
405-
-t $(REGISTRY)/feature-server-python-aws:$$VERSION \
406-
-f sdk/python/feast/infra/feature_servers/aws_lambda/Dockerfile --load .
407-
408400
push-feature-transformation-server-docker:
409401
docker push $(REGISTRY)/feature-transformation-server:$(VERSION)
410402

‎docs/SUMMARY.md‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -118,9 +118,7 @@
118118
* [Feature servers](reference/feature-servers/README.md)
119119
* [Python feature server](reference/feature-servers/python-feature-server.md)
120120
* [\[Alpha\] Go feature server](reference/feature-servers/go-feature-server.md)
121-
* [\[Alpha\] AWS Lambda feature server](reference/feature-servers/alpha-aws-lambda-feature-server.md)
122121
* [Offline Feature Server](reference/feature-servers/offline-feature-server)
123-
124122
* [\[Beta\] Web UI](reference/alpha-web-ui.md)
125123
* [\[Alpha\] On demand feature view](reference/alpha-on-demand-feature-view.md)
126124
* [\[Alpha\] Data quality monitoring](reference/dqm.md)

‎docs/getting-started/faq.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ The list of supported offline and online stores can be found [here](../reference
9595

9696
### Does Feast support using different clouds for offline vs online stores?
9797

98-
Yes. Using a GCP or AWS provider in `feature_store.yaml` primarily sets default offline / online stores and configures where the remote registry file can live (Using the AWS provider also allows for deployment to AWS Lambda). You can override the offline and online stores to be in different clouds if you wish.
98+
Yes. Using a GCP or AWS provider in `feature_store.yaml` primarily sets default offline / online stores and configures where the remote registry file can live. You can override the offline and online stores to be in different clouds if you wish.
9999

100100
### What is the difference between a data source and an offline store?
101101

‎docs/reference/feature-servers/README.md‎

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,7 @@ Feast users can choose to retrieve features from a feature server, as opposed to
88

99
{% content-ref url="go-feature-server.md" %}
1010
[go-feature-server.md](go-feature-server.md)
11-
{% endcontent-ref %}
12-
13-
{% content-ref url="alpha-aws-lambda-feature-server.md" %}
14-
[alpha-aws-lambda-feature-server.md](alpha-aws-lambda-feature-server.md)
11+
=======
1512
{% endcontent-ref %}
1613

1714
{% content-ref url="offline-feature-server.md" %}

‎docs/reference/feature-servers/alpha-aws-lambda-feature-server.md‎

Lines changed: 0 additions & 197 deletions
This file was deleted.

‎docs/reference/feature-servers/python-feature-server.md‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,6 @@ There is a CLI command that starts the server: `feast serve`. By default, Feast
1212

1313
One can deploy a feature server by building a docker image that bundles in the project's `feature_store.yaml`. See this [helm chart](https://github.com/feast-dev/feast/blob/master/infra/charts/feast-feature-server) for an example on how to run Feast on Kubernetes.
1414

15-
A [remote feature server](alpha-aws-lambda-feature-server.md) on AWS Lambda is also available.
16-
1715
## Example
1816

1917
### Initializing a feature server

‎sdk/python/feast/constants.py‎

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,6 @@
1717
# Maximum interval(secs) to wait between retries for retry function
1818
MAX_WAIT_INTERVAL: str = "60"
1919

20-
AWS_LAMBDA_FEATURE_SERVER_IMAGE = "feastdev/feature-server-python-aws"
21-
AWS_LAMBDA_FEATURE_SERVER_REPOSITORY = "feast-python-server"
22-
2320
# feature_store.yaml environment variable name for remote feature server
2421
FEATURE_STORE_YAML_ENV_NAME: str = "FEATURE_STORE_YAML_BASE64"
2522

@@ -44,8 +41,5 @@
4441
# Default offline server port
4542
DEFAULT_OFFLINE_SERVER_PORT = 8815
4643

47-
# Environment variable for feature server docker image tag
48-
DOCKER_IMAGE_TAG_ENV_NAME: str = "FEAST_SERVER_DOCKER_IMAGE_TAG"
49-
5044
# Default feature server registry ttl (seconds)
5145
DEFAULT_FEATURE_SERVER_REGISTRY_TTL = 5

‎sdk/python/feast/errors.py‎

Lines changed: 0 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -350,32 +350,6 @@ def __init__(self, feature_view_name: str):
350350
)
351351

352352

353-
class RepoConfigPathDoesNotExist(Exception):
354-
def __init__(self):
355-
super().__init__("The repo_path attribute does not exist for the repo_config.")
356-
357-
358-
class AwsLambdaDoesNotExist(Exception):
359-
def __init__(self, resource_name: str):
360-
super().__init__(
361-
f"The AWS Lambda function {resource_name} should have been created properly, but does not exist."
362-
)
363-
364-
365-
class AwsAPIGatewayDoesNotExist(Exception):
366-
def __init__(self, resource_name: str):
367-
super().__init__(
368-
f"The AWS API Gateway {resource_name} should have been created properly, but does not exist."
369-
)
370-
371-
372-
class IncompatibleRegistryStoreClass(Exception):
373-
def __init__(self, actual_class: str, expected_class: str):
374-
super().__init__(
375-
f"The registry store class was expected to be {expected_class}, but was instead {actual_class}."
376-
)
377-
378-
379353
class FeastInvalidInfraObjectType(Exception):
380354
def __init__(self):
381355
super().__init__("Could not identify the type of the InfraObject.")

0 commit comments

Comments
 (0)