Seeds: Set all environments to use a privileged execution

While we generally discourage the use of the privileged executions for production usage, the existing setup with the outdated execution environments broke. Therefore, we should switch our seed data to feature the latest Docker images.
This commit is contained in:
Sebastian Serth
2023-02-15 19:13:26 +01:00
parent 4b4942ef08
commit 0e4cd91ef7
2 changed files with 8 additions and 2 deletions

View File

@ -30,6 +30,9 @@ ExecutionEnvironment.create_factories user: admin
# submissions
FactoryBot.create(:submission, exercise: @exercises[:fibonacci], user: external_user)
# The old images included in the seed data do not feature a dedicated `user` and therefore require a privileged execution.
ExecutionEnvironment.update_all privileged_execution: true # rubocop:disable Rails/SkipsModelValidations
say(<<~CONFIRMATION_MESSAGE)
Development data has been seeded successfully.
@ -37,7 +40,7 @@ say(<<~CONFIRMATION_MESSAGE)
stored in the database. However, these haven't been yet \
synchronized with a runner management. Please take care \
to configure a runner management according to the \
documentation and synchronize environments thorugh the \
documentation and synchronize environments through the \
user interface. To do so, open `/execution_environments` \
and click on the "Synchronize all" button.
CONFIRMATION_MESSAGE

View File

@ -28,6 +28,9 @@ ExecutionEnvironment.create_factories user: admin
# exercises
Exercise.create_factories user: admin
# The old images included in the seed data do not feature a dedicated `user` and therefore require a privileged execution.
ExecutionEnvironment.update_all privileged_execution: true # rubocop:disable Rails/SkipsModelValidations
say(<<~CONFIRMATION_MESSAGE)
Production data has been seeded successfully.
@ -41,7 +44,7 @@ say(<<~CONFIRMATION_MESSAGE)
stored in the database. However, these haven't been yet \
synchronized with a runner management. Please take care \
to configure a runner management according to the \
documentation and synchronize environments thorugh the \
documentation and synchronize environments through the \
user interface. To do so, open `/execution_environments` \
and click on the "Synchronize all" button.
CONFIRMATION_MESSAGE