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

Ensure Default InstanceType is enabled for Default TeamType in clean install (backport #2573) #2577

Merged
merged 3 commits into from
Aug 10, 2023

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented Aug 9, 2023

Backport of #2573


Fixes #2572

Description

Ensures the default instanceType is enabled for the default TeamType in a clean install

This will need backporting once merged.

This also tidies up the TeamType edit dialog:

  • removes the 'billing description' field for instances when billing isn't enabled
  • improves the heading shown against the individual instance types
  • hides the whole features table as it is not functional yet.

Finally, noticed a spurious log message from sequelize around creating the default ProjectStack - we were passing in default values for non-existent properties of the Stack object. Now tidied up.

Checklist

  • I have read the contribution guidelines
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
  • Changes flowforge.yml?
  • Issue/PR raised on flowforge/helm to update ConfigMap Template
  • Issue/PR raised on flowforge/CloudProject to update values for Staging/Production

Labels

  • Backport needed? -> add the backport label
  • Includes a DB migration? -> add the area:migration label

@hardillb hardillb merged commit 69c9914 into maintenance Aug 10, 2023
@hardillb hardillb deleted the backport-2573 branch August 10, 2023 08:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants