Ensure Default InstanceType is enabled for Default TeamType in clean install (backport #2573) #2577
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
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
flowforge.yml
?flowforge/helm
to update ConfigMap Templateflowforge/CloudProject
to update values for Staging/ProductionLabels
backport
labelarea:migration
label