Skip to content
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.

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

add env for roboflow serverless service #1059

Merged
merged 9 commits into from
Mar 7, 2025
Merged

Conversation

PacificDou
Copy link
Collaborator

@PacificDou PacificDou commented Feb 27, 2025

Description

  1. add env for roboflow serverless service: GCP_SERVERLESS
  2. switch http_client's mode to v0 for serverless domains, since we'll not support endpoints /model/* which are required by mode v1
  3. temporarily disable endpoints /infer/* because our authoriser does not support api_key in json body, will enable these endpoints later when we updated the authorizer

List any dependencies that are required for this change.

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • This change requires a documentation update

How has this change been tested, please provide a testcase or example of how you tested the change?

Tested in staging

Any specific deployment considerations

For example, documentation changes, usability, usage/costs, secrets, etc.

Docs

  • Docs updated? What were the changes:

@@ -515,3 +515,5 @@
)
if IGNORE_MODEL_DEPENDENCIES_WARNINGS:
warnings.simplefilter("ignore", ModelDependencyMissing)

IS_ROBOFLOW_SERVERLESS = str2bool(os.getenv("IS_ROBOFLOW_SERVERLESS", "False"))
Copy link
Contributor

@grzegorz-roboflow grzegorz-roboflow Feb 27, 2025

Choose a reason for hiding this comment

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

I'd vote for changing this variable name to something more specific, i.e. GCP_SERVERLESS.
Or we could reuse LAMBDA instead of introducing new env variable - it would make sense to reuse LAMBDA since we are going to replicate AWS (with Redis and offloader)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

let's go GCP_SERVERLESS

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

updated

@PawelPeczek-Roboflow PawelPeczek-Roboflow merged commit 5602d23 into main Mar 7, 2025
30 checks passed
@PawelPeczek-Roboflow PawelPeczek-Roboflow deleted the serverless-envs branch March 7, 2025 17:51
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.

3 participants