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

sep-workers-by-type-sidekiq-env #832

Merged
merged 18 commits into from
Feb 22, 2024
Merged

Conversation

aprilrieger
Copy link
Collaborator

@aprilrieger aprilrieger commented Feb 21, 2024

Trying to establish a pattern of passing the variables from both the original workers extraEnvVars and the import workers extraEnvVars

Screenshot 2024-02-21 at 23 49 16

…he dev user will still see the pattern and know how to use it
…so tried getting the variable excluded, and then try to include it the same way, but that didnt work. So now trying to explicitly add it back to pass to the deployment - heavy sigh -
…he worker script. And only set that env variable in the importWorker so that the reg worker will just use the default or one set in the deployment extraEnvVars
@aprilrieger
Copy link
Collaborator Author

Deployed successfully to demo and see that the correct amount of threads are correct as expected form the deploy.
Screenshot 2024-02-21 at 23 49 16

@bkiahstroud bkiahstroud merged commit dc44953 into develop Feb 22, 2024
6 checks passed
@bkiahstroud bkiahstroud deleted the sep-workers-by-type-sidekiq-env branch February 22, 2024 17:18
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