| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
The current approach requires catching exceptions to handle these errors
and callers are already handling model validations so it seems more
appropriate. Also it seemed to convoluted to add this logic directly to
the model since the model needs to check too many possible associations
to determine whether or not there are more than one cluster since the
model doesn't know what it's being created on. Additionally we only
wanted to validate during create to avoid the risk of existing models
becoming invalid by many different edge cases.
|
| |
|
|
|
|
| |
Now we have terminals for instance and group clusters we can remove the
FF now. Deploying to instance clusters has been working without
complaints too.
|
| | |
|
| |
|
|
| |
Try to simplify feature flag checks by using policies
|
| |
|
|
|
| |
Instance level clusters were already mostly supported, this change adds
admin area controllers for cluster CRUD
|
| |
|
|
|
| |
- maintainer for group can read, create, update, and admin cluster
- project user, at any level, cannot do anything with group cluster
|
| |
|
|
|
|
|
|
|
| |
Enable frozen string in:
* app/presenters
* app/policies
Partially addresses #47424.
|
| | |
|
| |
|
