[Feature flag] Enable `jira_connect_asymmetric_jwt`

Summary

This issue is to rollout Jira Connect asymmetric JWTs on production, that is currently behind the jira_connect_asymmetric_jwt feature flag.

Owners

• Team: ~"group::integrations"
• Most appropriate slack channel to reach out to: #g_ecosystem_integrations
• Best individual to reach out to: @Andysoiron
• PM: @mushakov

Stakeholders

Expectations

What are we expecting to happen?

• Installing and uninstalling Jira Connect apps should work without a visible change.
• The app descriptor should contain 'signed-install': true.

What might happen if this goes wrong?

• Installing and uninstalling Jira Connect apps might fail.

What can we monitor to detect problems with this?

• Events Controller logs

Rollout Steps

Rollout on non-production environments

• Ensure that the feature MRs have been deployed to non-production environments.
  • /chatops run auto_deploy status 59cf343b
• Enable the feature globally on non-production environments.
  • /chatops run feature set jira_connect_asymmetric_jwt true --dev
  • /chatops run feature set jira_connect_asymmetric_jwt true --staging
• Verify that the feature works as expected. Posting the QA result in this issue is preferable.

Global rollout on production

All /chatops commands that target production should be done in the #production slack channel for visibility.

• Enable the feature globally on production environment.
  • /chatops run feature set jira_connect_asymmetric_jwt true
• Announce on the feature issue that the feature has been globally enabled.
• Wait for at least one day for the verification term.

Release the feature

After the feature has been deemed stable, the clean up should be done as soon as possible to permanently enable the feature and reduce complexity in the codebase.

• Create a merge request to remove jira_connect_asymmetric_jwt feature flag. Ask for review and merge it.
  • Remove all references to the feature flag from the codebase.
  • Remove the YAML definitions for the feature from the repository.
  • Create a changelog entry.
• Ensure that the cleanup MR has been deployed to both production and canary. If the merge request was deployed before the code cutoff, the feature can be officially announced in a release blog post.
  • /chatops run auto_deploy status <merge-commit-of-cleanup-mr>
• Close the feature issue to indicate the feature will be released in the current milestone.
• Clean up the feature flag from all environments by running these chatops command in #production channel:
  • /chatops run feature delete jira_connect_asymmetric_jwt --dev
  • /chatops run feature delete jira_connect_asymmetric_jwt --staging
  • /chatops run feature delete jira_connect_asymmetric_jwt
• Close this rollout issue.

Rollback Steps

• This feature can be disabled by running the following Chatops command:

/chatops run feature set jira_connect_asymmetric_jwt false