Releases: Roche/foxops
v2.1.0 - Added Support for a "local" Hoster
foxops now supports running in a configuration that doesn't require an external Gitlab instance.
This mode is mostly useful for development and running it locally in 3rd party components.
Breaking Changes
When starting foxops, GitLab now must be explicitly selected as the hoster. Also, the environment variables which are used to configure the GitLab settings changed. Please use the new ones:
FOXOPS_HOSTER_TYPE=gitlab
FOXOPS_HOSTER_GITLAB_ADDRESS=https://my.gitlab.com
FOXOPS_HOSTER_GITLAB_TOKEN=glpat-abcdefg
v2.0.0 - New UI & HTTP API
This major release basically contains a complete rewrite of foxops with a completely new architecture.
While the previous version was a pure CLI tool that was intended to be used in combination with a CI pipeline, from this version on foxops is meant to be run as a service which provides a full-fledged web UI and HTTP API.
New Features
- foxops now is intended to run as a service. A docker image is provided to easily deploy it.
- a user-friendly UI is provided to manually manage individual and also large amounts of incarnations
- all functionality is also accessible via an HTTP API that can be used in custom automations
- the HTTP API is documented using an OpenAPI schema and (accessible via
/docs
URL, thanks to fastapi) - incarnations can be managed using a custom terraform provider
Documentation
find it on https://foxops.readthedocs.io/
v2.0.0-alpha.5: fix for .png file if it is defined in excluded_files (#385)
* fix for .png file if it is defined in excluded_files * Add test case for rendering when binary file is excluded * Fix for linting and typing issues
v2.0.0-alpha.4
This release removes a lot of legacy code - and with that, also support for incarnations that were supported with an old version of foxops (pre 2.0.0-alpha3), and have not been migrated yet.
Before updating to this version, make sure that you already upgraded to 2.0.0-alpha.3 and followed the migration steps.
Last Release to Support Legacy Incarnations and reconcile command
the next release will contain a lot of removals of legacy code.
Make sure to upgrade all incarnations to the new data format as described in the v2.0.0-alpha.2 release and make sure there are no leftovers.
New data model
Foxops now keeps track of changes to an incarnation in its own database
Upgrade from last version
The new data model requires a data migration. The best way to do that is by calling the upgrade_all_incarnations
endpoint:
curl -X POST 'https://your-foxops-instance/api/incarnations/upgrade-all?delete_nonexisting=true'
The delete_nonexisting
parameter causes incarnations to be deleted which no longer exist in the Gitlab instance (it's a leftover cleanup)
Initial release of foxops v2 with the API
v2.0.0-alpha.1 Merge pull request #97 from Roche/ef85dependabot/pip/black-22.8.0
v1.6.5
Fixed updating with large git diffs
Full Changelog: v1.6.4...v1.6.5
v1.6.4
v1.6.3
Install bash in container image deployment