- no longer using.

- better visibility

The subscription banner should be shown for all group pages/subpages as
well as all project pages/subpages.

Finishes https://gitlab.com/gitlab-org/growth/product/-/issues/1557

The plan for RSpec 4.0 is to disable monkey patching:
https://rspec.info/blog/2013/07/the-plan-for-rspec-3/#zero-monkey-patching-mode

This commit stops using RSpec monkey patching:
https://relishapp.com/rspec/rspec-core/docs/configuration/zero-monkey-patching-mode

decorated_subscription is expected to return nil
when there is no subscription. It was previously returning an empty
SubscriptionDecorator object and caused breakage.

This change corrects the behavior, in tune with what the
Gitlab::ExpiringSubscriptionMessage expects.

This is part of: https://gitlab.com/gitlab-org/gitlab/-/issues/214212

This reverts commit 14ebe68c.

This reverts commit 1206dac4, reversing
changes made to b93dbdf7.

Removes some keyword arguments within LicenseHelper
Passes some licenses to the helper from the view for
optimization

After the removal of memoization, the current_license method
on the LicenseHelper is deprecated
Also some places are optimized to pass the license as a param

These changes increase the scope and are not directly related to
the changes. Will move those as a follow up
This commit is intended to be squashed

LicenseHelper uses extend self
- memoized data is stored at the module level
- is cached for the life of the process
- this is not the intended result
Move upgrade_plan_url to the EE::GitlabRoutingHelper

.com users are informed that their subscription is going to expire, or
is expired, and provided an easy path to update/renew their
subscription.

We've previously had a similar message for self-managed users, this
commit brings the message over to .com

* only display to expired accounts for 30 days

part of: https://gitlab.com/gitlab-org/growth/product/-/issues/102

Update the messaging and styling of the renewal banner. This is one of a
series of commits to getting the banner to be more helpful for customers
who are trying to renew.

part of: https://gitlab.com/gitlab-org/growth/product/-/issues/102

I'll be working in this area and decided to backfill the test suite so
it'd be more easily refactorable for the feature I'm working on. In the
process I also added I18n suport.

At first glance one could argue this has duplicate language and could be
more concise, but I found it difficult to follow the GitLab best
practices for externalization (particularly "splitting sentences")
in it's previous implementation.

I also felt like although the code was more concise before, it was
fairly difficult to parse, and more difficult to extend.

* backfill license_helper_spec
* refactor license_helper

I've followed the best practices outlined here:
https://docs.gitlab.com/ee/development/i18n/externalization.html#best-practices

This is part of:
https://gitlab.com/gitlab-org/growth/product/-/issues/102

We already show this message on the web so this is not needed

We should not use `ActiveRecord::Base.connected?` to
check if a DB exists because that only checks if a
connection is already established. It's possible
for the DB to exist but a connection has not yet
been established.

I noticed that this method in the initializer was
wrong but we didn't notice it because this method
was never invoked.

0_license.rb is run before any connections are
established so `connected?` always returned false
even if the table exists.

I've also fixed other places that use the same check
even though they might not be having problems because
a connection is already established at that point.

Add a FAQ link to the license we display to users when their license is
expired, or is about to expire.

finishes:
https://gitlab.com/gitlab-org/gitlab/issues/7681

Provide more information to self-managed users to limit the confusion
they might have while renewing. This new information will be referenced
in emails coming from the Customer app.

* Add the License#current_active_user_count to the admin dashboard
* add a current_active_user_count helper method

part of: https://gitlab.com/gitlab-org/growth/engineering/issues/40/

Ran: bundle exec rubocop --only RSpec/EmptyLineAfterFinalLet -a ee/

Brian Kabiro authored 5 years ago and James Lopez committed 5 years ago

- add `maximum_user_count` to License model and view helpers
- add `maximum_user_count` to the API response`

https://gitlab.com/gitlab-org/gitlab/issues/27703

Remove additional text if current user count exceeds historical.

Signed-off-by: Rémy Coutable <remy@rymai.me>

- Allow the message to be returned from git_http controller
- Strip html chars from message returned via API

Add more usage data to EE ping

This MR loads the EE usage ping asynchronously on the admin application settings page and now includes the counts of the following items:

* Comments
* Groups
* Users
* Projects
* Issues
* Labels
* CI builds
* Snippets
* Milestones
* Todos
* Pushes
* Merge requests
* Environments
* Triggers
* Deploy keys
* Pages
* Project Services
* Issue Boards
* CI Runners
* Deployments
* Geo Nodes
* LDAP Groups
* LDAP Keys
* LDAP Users
* LFS objects
* Protected branches
* Releases
* Remote mirrors
* Web hooks

Closes #997

See merge request !735

Load it asynchronously to prevent blocking a page load.

Closes #997

Add a container around usage data help-block to prevent horizontal scroll in Firefox

Closes #808

See #393

Closes #610

Closes #607

That way admins can have a quick link at hand to upload the license.

Closes #393