Skip to content

fix(service): restrict service.type to WMS, WFS, and WMTS - #102

Merged
fjlopez merged 1 commit into
devfrom
fix/restrict-service-types
Oct 20, 2026
Merged

fjlopez merged 1 commit into
devfrom
fix/restrict-service-types

Conversation

@fjlopez

@fjlopez fjlopez commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

Why

Development, postgres, and oracle databases can still list AIMS, FME, and TC after an older changelog. New Liquibase changesets remove those service.type values. A stored service of another type stays in the database.

What changed

  • The development, postgres, and oracle changelogs delete the extra code-list values.
  • The admin service form test expects only WMS, WFS, and WMTS.
  • The backend pointer includes the client profile filter.

Scope

  • The three profile trees, the admin type list, and the backend pointer.
  • Stored service rows stay in the database.
  • The existing development cleanup changeset stays as it is.

Blast Radius

The next Liquibase run removes those code-list values. Service rows stay. Viewers follow the backend profile filter once that change is deployed.

Verification

  • python3 tools/tests/test_changelog_immutability.py passed, 18 tests.
  • Playwright e2e/admin/forms/service-type-options.spec.ts passed with the admin auth setup, 2 tests.

Fixes #101.

Liquibase drops the other code-list values. A stored service of another type stays in the database.
@fjlopez
fjlopez merged commit c49b8dd into dev Oct 20, 2026
16 checks passed
fjlopez added a commit that referenced this pull request Oct 20, 2026
Stack #102 pinned pre-squash commit 140c337d. The fix is on backend origin/dev as 73840f75.
@fjlopez
fjlopez deleted the fix/restrict-service-types branch October 20, 2026 23:04
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.

1 participant