Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add hostname to project settings #1344

Closed
Pezmc opened this issue Dec 1, 2022 · 5 comments
Closed

Add hostname to project settings #1344

Pezmc opened this issue Dec 1, 2022 · 5 comments
Assignees
Labels
task A piece of work that isn't necessarily tied to a specific Epic or Story.

Comments

@Pezmc
Copy link
Contributor

Pezmc commented Dec 1, 2022

Description

Project > Settings > Hostname

Needs validation:

  • Host names need to be valid and unique across all projects
  • Is a valid hostname

Only shown if the Custom Domains feature is enabled, which is based on the current team type.

Epic/Story

#324

@Pezmc Pezmc added the task A piece of work that isn't necessarily tied to a specific Epic or Story. label Dec 1, 2022
@Pezmc Pezmc self-assigned this Dec 1, 2022
@Pezmc
Copy link
Contributor Author

Pezmc commented Dec 1, 2022

@ZJvandeWeg @knolleary I'm not clear on the business logic for displaying/hiding the custom domains feature. Is that as yet undecided? Should we have a discussion?

@ZJvandeWeg
Copy link
Member

@Pezmc I'm not sure what the problem is, some views are hidden already based on license I assume? For example billing?

As I understand it, can't we check if the EE license was applied?

@hardillb
Copy link
Contributor

hardillb commented Dec 1, 2022

@ZJvandeWeg I thought this was going to be a premium feature, e.g. one available when using something other than the basic team type (and hence paying more for it)

@knolleary
Copy link
Member

They will be a premium feature - which means the configuration options should only be available on an EE licensed instance.

What we haven't resolved is what that means in FF Cloud - which is an EE licensed instance.

The pricing principles we set out in the summer suggested that the existing Team Type we have should represent the Community level of functionality. Any new features we add that are EE licensed would be exposed in FF Cloud via a new tier of Team that comes at additional cost.

As it stands, we have not defined what that tier is, what the pricing model would be etc. We did some work to introduce the TeamType concept to the platform in a previous release. But there will be more work to do when it comes to actually introducing the new higher tier - including technical, messaging, pricing etc.

So the question is:

  • do we make this feature available to all teams on FF Cloud
    • most simple option - can gate it all on whether a license is applied or not
  • do we introduce the higher tier team in this release to include this feature?
    • will require a few days of additional work to get the technical/non-technical requirements defined for adding a new tier

My main concern at this stage of the release is the additional work needed to introduce a new Team Tier - not just technical, but all the pricing/website/messaging updates it requires and we're pretty fully committed right now.

@Pezmc Pezmc closed this as completed Dec 6, 2022
@Pezmc Pezmc closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2022
@Pezmc
Copy link
Contributor Author

Pezmc commented Dec 15, 2022

Closed this issue as the custom hostname work was put on hold, more information in #324 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task A piece of work that isn't necessarily tied to a specific Epic or Story.
Projects
Archived in project
Development

No branches or pull requests

4 participants