Added enable function to schemas. This allows filtering of schemas
which is a required part of feature flagging in rancher. Added
addFeature functions to controller template for adding handlers that
can be disabled if their associated feature is disabled.
Now, identifies and assigns namespaces. Prior, the
backend listed items belongng to all namespaces in
all projects no matter what because they were not
being tracked. This led to longer request times
for projects that contained a fraction of total
resources. Now, rancher can filter project
resource requests; times are improved and
largely dependent on resource amount for the given
project.
This change makes it so that schemas can be replaced when they already exist.
This is to support the ability for kontainer drivers to update their dynamic
schemas.
Issue:
https://github.com/rancher/rancher/issues/17712
This change adds a dynamic field indicator to the field struct. This is so
we can remove the dynamic fields from an existing schema before merging the
dynamic schema and actual schema to prevent removed dynamic fields form being
incorrectly left behind on the schema.
Issue:
https://github.com/rancher/rancher/issues/12698
Problem:
Pagination is not showing up
Solution:
Pagination was being created properly but then dropped in favor of an
empty version. Save the pagination on the context so it can be accessed
later and not reset.
This change adds an early panic if the type of the obj supplied to the
`MustImport` func is a pointer. This is to prevent a later, cryptic,
error that is not as clear to diagnose.
This change gives norman the ability to filter api requests based on the
default value of fields. Before, it would filter on the actual data in
the resource, and then apply default values to the resource before
returning.
Issue:
https://github.com/rancher/rancher/issues/13418
- Do not drop a field-to-annotation conversion if the value of the field is
nil. The user is excplicitly trying to set it to nil
- Never delete field annotations, even if they are not in the new map of
annotations sent by the user.
- Prevent the modification of the creatorId field, which is a special case
field that should be considered protected
