gitlab-org--gitlab-foss/spec/migrations/generate_lets_encrypt_private_key_spec.rb

# frozen_string_literal: true

require 'spec_helper'
require_migration!

RSpec.describe GenerateLetsEncryptPrivateKey do
  describe '#up' do
    it 'does not fail' do
      expect do
        described_class.new.up
      end.not_to raise_error
    end
  end
end
Add latest changes from gitlab-org/gitlab@master 2019-10-21 23:06:00 -04:00			`# frozen_string_literal: true`

Store Let's Encrypt private key in settings Storing this key in secrets.yml was a bad idea, it would require users using HA setups to manually replicate secrets across nodes during update, it also needed support from omnibus package * Revert "Generate Let's Encrypt private key" This reverts commit 444959bfa0b79e827a2a1a7a314acac19390f976. * Add Let's Encrypt private key to settings as encrypted attribute * Generate Let's Encrypt private key in database migration 2019-05-28 00:47:34 -04:00			`require 'spec_helper'`
Add latest changes from gitlab-org/gitlab@master 2021-06-11 14:10:13 -04:00			`require_migration!`
Store Let's Encrypt private key in settings Storing this key in secrets.yml was a bad idea, it would require users using HA setups to manually replicate secrets across nodes during update, it also needed support from omnibus package * Revert "Generate Let's Encrypt private key" This reverts commit 444959bfa0b79e827a2a1a7a314acac19390f976. * Add Let's Encrypt private key to settings as encrypted attribute * Generate Let's Encrypt private key in database migration 2019-05-28 00:47:34 -04:00
Add latest changes from gitlab-org/gitlab@master 2020-06-24 14:09:03 -04:00			`RSpec.describe GenerateLetsEncryptPrivateKey do`
Store Let's Encrypt private key in settings Storing this key in secrets.yml was a bad idea, it would require users using HA setups to manually replicate secrets across nodes during update, it also needed support from omnibus package * Revert "Generate Let's Encrypt private key" This reverts commit 444959bfa0b79e827a2a1a7a314acac19390f976. * Add Let's Encrypt private key to settings as encrypted attribute * Generate Let's Encrypt private key in database migration 2019-05-28 00:47:34 -04:00			`describe '#up' do`
Generate lets_encrypt_private_key on the fly Remove migration generating lets encrypt key Don't generate private_key if database is readonly For reference: This reverts commit 988a7f70489b99383b95e9f271a2caf6bb5b3a44. This reverts commit 21acbe531592d55caf0e5b8716a3b551dafd6233. 2019-05-31 01:22:55 -04:00			`it 'does not fail' do`
Store Let's Encrypt private key in settings Storing this key in secrets.yml was a bad idea, it would require users using HA setups to manually replicate secrets across nodes during update, it also needed support from omnibus package * Revert "Generate Let's Encrypt private key" This reverts commit 444959bfa0b79e827a2a1a7a314acac19390f976. * Add Let's Encrypt private key to settings as encrypted attribute * Generate Let's Encrypt private key in database migration 2019-05-28 00:47:34 -04:00			`expect do`
Generate lets_encrypt_private_key on the fly Remove migration generating lets encrypt key Don't generate private_key if database is readonly For reference: This reverts commit 988a7f70489b99383b95e9f271a2caf6bb5b3a44. This reverts commit 21acbe531592d55caf0e5b8716a3b551dafd6233. 2019-05-31 01:22:55 -04:00			`described_class.new.up`
Store Let's Encrypt private key in settings Storing this key in secrets.yml was a bad idea, it would require users using HA setups to manually replicate secrets across nodes during update, it also needed support from omnibus package * Revert "Generate Let's Encrypt private key" This reverts commit 444959bfa0b79e827a2a1a7a314acac19390f976. * Add Let's Encrypt private key to settings as encrypted attribute * Generate Let's Encrypt private key in database migration 2019-05-28 00:47:34 -04:00			`end.not_to raise_error`
			`end`
			`end`
			`end`