Webservice: enable per-deployment blackoutSeconds

What does this MR do?

Webservice: enable per-deployment blackoutSeconds

Enable configuration of `shutdown.blackoutSeconds` on a per-deployment
basis by using environment variable that is populated into `gitlab.yml`
by the template at the time of execution.

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

• Merge Request Title and Description are up to date, accurate, and descriptive
• MR targeting the appropriate branch
• MR has a green pipeline on GitLab.com

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes
• [] Documentation created/updated already documented as inherited. Now employed.
• Tests added
• Integration tests added to GitLab QA

Closes #2543 (closed)

changed milestone to %13.10

added Deliverable devopssystems groupdistribution kubernetes-migration-blocker priority3 sectioncore platform typefeature wg_k8s-migration workflowready for review labels

mentioned in issue #2543 (closed)

added 1 commit

• 25f2d05e - Webservice: enable per-deployment blackoutSeconds

Compare with previous version

	1 Warning
⚠	Please check the QA job and compare with builds on master. If no new failures are reported in QA job, add 'QA:verified' label.

1 Message

📖

Please add the workflowready for review label once you think the MR is ready to for an initial review. If from a community member, ask that the Community contribution label be added as well. Merge requests are handled according to the workflow documented in our handbook and should receive a response within the limit documented in our First-response SLO. If you don't receive a response, please mention @gitlab-org/distribution, or one of our Project Maintainers

Generated by 🚫 Danger

requested review from @jarv

assigned to @WarheadsSE

resolved all threads

added 1 commit

• 6bbc5e7f - Apply 2 suggestion(s) to 1 file(s)

Compare with previous version

@WarheadsSE is it better that we set the environment variable here or in settings https://gitlab.com/gitlab-org/gitlab/-/blob/7ff0058a15bbedce3657d5fd5b8b0d67bd2c8b68/config/initializers/1_settings.rb#L883 . I feel like putting it in settings is more consistent with other configuration, but I guess this works as well.

assigned to @jarv

resolved all threads

approved this merge request

LGTM

removed review request for @jarv

added workflowin review label and removed workflowready for review label

assigned to @twk3 and unassigned @WarheadsSE and @jarv