Skip to content

Comments

chore(build) manually migrate to uv#3114

Draft
cgoetz-inovex wants to merge 2 commits intomainfrom
chore/STACKITSDK-321_migrate-uv
Draft

chore(build) manually migrate to uv#3114
cgoetz-inovex wants to merge 2 commits intomainfrom
chore/STACKITSDK-321_migrate-uv

Conversation

@cgoetz-inovex
Copy link
Contributor

  • run uvx migrate-to-uv for core and services/*
  • manually add: [tool.uv.sources] stackit-core = { path = "../../core" } to eachs services pyproject.toml This lets the service use core from the source tree instead
  • adapt makefiles, scripts and workflows to use uv

STACKITSDK-321

Description

First step of migration to uv. Migrated each service here manually and adapted makefiles etc. to use uv.
When this is merged the corresponding PR in the generator can be merged.

Checklist

  • Issue was linked above
  • No generated code was adjusted manually (check comments in file header)
  • Changelogs and versioning
    • Changelog in root directory was adjusted (see here)
    • Changelog of the service(s) was adjusted (see e.g. here)
    • pyproject.toml of the service(s) was adjusted (see e.g. here)
  • Examples were added / adjusted (see examples/ directory)
  • Unit tests got implemented or updated
  • Unit tests are passing: make test (will be checked by CI)
  • No linter issues: make lint (will be checked by CI)

- run `uvx migrate-to-uv` for `core` and `services/*`
- manually add:
  [tool.uv.sources]
  stackit-core = { path = "../../core" }
  to eachs services `pyproject.toml`
  This lets the service use core from the source tree instead
- adapt makefiles, scripts and workflows to use uv

STACKITSDK-321
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