Skip to content

Conversation

@timma-yelp
Copy link
Contributor

@timma-yelp timma-yelp commented Dec 5, 2025

  1. Moved the scs conf from --conf to env var
  2. Adjusted the test cases accordingly
  3. Added the other required AWS properties to env var
  4. Upgraded service_configuration_lib to 3.3.7
  5. paasta validate ran successfully

@timma-yelp timma-yelp requested a review from a team as a code owner December 5, 2025 13:04
environment = instance_config.get_env_dictionary() # type: ignore

# Pop out scs_conf from spark_conf and store it in the environment, in sync with the tron_tools code
environment["SCS_CONF_STR"] = spark_conf.pop("scs_conf", None)
Copy link
Member

Choose a reason for hiding this comment

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

imo, it'll probably be a little more robust to have individual env vars for all the data we'd pass down (several of which already exist) so that we don't have to worry about ensuring that this string is always valid json

...but maybe this won't be a problem!

@nemacysts nemacysts merged commit d9aa330 into master Dec 8, 2025
8 checks passed
cuza added a commit that referenced this pull request Dec 16, 2025
…w-terminating-pods

* master:
  Released 1.36.3 via make release
  Moved the scs conf from --conf to env var (#4177)
  Released 1.36.2 via make release
  Revert "remove some unused code."
  Released 1.36.1 via make release
  Revert "Merge pull request #4151 from Yelp/timma/upgrade_spark_configuration_lib_to_3.3.7" (#4174)
  Released 1.36.0 via make release
  Released 1.35.8 via make release
  remove some mesos-isms from local-run
  remove some unused code.
  Changed the expected_scs_conf to json instead of raw string
  Changed the user to null in scs_conf which fixes the failing tron_tools test
  Upgraded service configuration lib to 3.3.7 and updated the test accordingly
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