You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two confusing aspects of the config for catalog-backend-module-okta
The config.d.ts does not match the expectation of catalog.providers.okta being a configArray, see here
A schedule is expected to be defined like catalog.providers.okta[0].frequency (see code) rather than as a schedule object like catalog.providers.okta[0].schedule. The latter seems to be the common approach in backstage, see this example.
Feature Suggestion
Specify the expectation of a schedule in the config.d.ts and support the frequently used approach of a schedule object.
There are two confusing aspects of the config for
catalog-backend-module-okta
The config.d.ts does not match the expectation of
catalog.providers.okta
being a configArray, see hereA schedule is expected to be defined like
catalog.providers.okta[0].frequency
(see code) rather than as a schedule object likecatalog.providers.okta[0].schedule
. The latter seems to be the common approach in backstage, see this example.Feature Suggestion
Specify the expectation of a schedule in the
config.d.ts
and support the frequently used approach of a schedule object.Context
@roadiehq/catalog-backend-module-okta v0.10.2
, using the new-backend-system as per the docs.The text was updated successfully, but these errors were encountered: