v5.2.0 wharf-api

Docker image

Hosted over at https://quay.io/repository/iver-wharf/wharf-api

docker pull quay.io/iver-wharf/wharf-api:v5.2.0

Changes (since v5.1.3)

• Added api field to engine response (in e.g GET /api/engine) that was added to the configuration in v5.1.0/#156. The field can currently only have two different values: (#185)

  • "jenkins-generic-webhook-trigger": Jenkins Generic Webhook Trigger plugin: https://plugins.jenkins.io/generic-webhook-trigger/

  • "wharf-cmd.v1": wharf-cmd-provisioner REST interface v1, which is an extension of the jenkins-generic-webhook-trigger. The build.workerId is only set in the database if the engine API is of this type.

• Fixed PUT /api/project/{projectId}/branch where it created invalid SQL statements to delete old branches. (#186)

v5.1.3 wharf-api

Docker image

Hosted over at https://quay.io/repository/iver-wharf/wharf-api

docker pull quay.io/iver-wharf/wharf-api:v5.1.3

Changes (since v5.1.2)

• Changed automatic JSON indentation in HTTP responses based on the user agent, so it no longer automatically indents for desktop, mobile, or tablet devices. It is still enabled for cURL and if the ?pretty flag is set. (#170)

• Changed Go runtime from v1.17 to v1.18. (#171)

• Changed version of github.com/swaggo/swag from v1.8.0 to v1.8.1. (#171)

• Added dependencies:

  • golang.org/x/text v0.3.7 (#173)
  • gopkg.in/typ.v4 v4.1.0. (#172, #181)

• Fixed gRPC logs streaming silently ignoring all logs after a pause between log lines. (#175, #180)

• Fixed PUT /api/build/{buildId}/status not returning the resulting updated build object, and changed to return status code 200 (OK) instead of 204 (No Content) on success. (#183)

v5.1.2 wharf-api

Docker image

Hosted over at https://quay.io/repository/iver-wharf/wharf-api

docker pull quay.io/iver-wharf/wharf-api:v5.1.2

Changes (since v5.1.1)

• Fixed token in trigger URL used in HTTP request getting redacted, instead of only the copy that is logged. (#166)

v5.1.1 wharf-api

Docker image

Hosted over at https://quay.io/repository/iver-wharf/wharf-api

docker pull quay.io/iver-wharf/wharf-api:v5.1.1

Changes (since v5.1.0)

• Fixed bug of failing migrations that was introduced in v5.1.0. (#161, #163)

v5.1.0 wharf-api

Docker image

Hosted over at https://quay.io/repository/iver-wharf/wharf-api

docker pull quay.io/iver-wharf/wharf-api:v5.1.0

Migration from v4.2.0 or earlier

Some manual SQL commands are needed. To run SQL commands on a Postgres found in Kubernetes, you could run the following:

$ kubectl exec -it wharf-db-0 -- psql -U postgres wharf
Password for user postgres:
psql (11.12)
Type "help" for help.

wharf=#

Then apply the following SQL:

BEGIN;
ALTER TABLE token RENAME COLUMN token TO value;

UPDATE token SET user_name='' WHERE user_name IS NULL;
ALTER TABLE token ALTER COLUMN user_name SET NOT NULL;
ALTER TABLE token ALTER COLUMN user_name SET DEFAULT '';

UPDATE project SET group_name='' WHERE group_name IS NULL;
ALTER TABLE project ALTER COLUMN group_name SET NOT NULL;
ALTER TABLE project ALTER COLUMN group_name SET DEFAULT '';

UPDATE project SET description='' WHERE description IS NULL;
ALTER TABLE project ALTER COLUMN description SET NOT NULL;
ALTER TABLE project ALTER COLUMN description SET DEFAULT '';

UPDATE project SET avatar_url='' WHERE avatar_url IS NULL;
ALTER TABLE project ALTER COLUMN avatar_url SET NOT NULL;
ALTER TABLE project ALTER COLUMN avatar_url SET DEFAULT '';

UPDATE project SET git_url='' WHERE git_url IS NULL;
ALTER TABLE project ALTER COLUMN git_url SET NOT NULL;
ALTER TABLE project ALTER COLUMN git_url SET DEFAULT '';

UPDATE project SET build_definition='' WHERE build_definition IS NULL;
ALTER TABLE project ALTER COLUMN build_definition SET NOT NULL;
ALTER TABLE project ALTER COLUMN build_definition SET DEFAULT '';

UPDATE artifact SET file_name='' WHERE file_name IS NULL;
ALTER TABLE artifact ALTER COLUMN file_name SET NOT NULL;
ALTER TABLE artifact ALTER COLUMN file_name SET DEFAULT '';

COMMIT;

Changes (since v5.0.0)

• Deprecated trigger configs (YAML: ci.triggerUrl & ci.triggerToken, environment variables: WHARF_CI_TRIGGERURL & WHARF_CI_TRIGGERTOKEN) in favor of new configuration values that allow specifying up to two different execution engines: (#134, #156)

  YAML	Environment variable	Type
  ci.engine.id	WHARF_CI_ENGINE_ID	string (max 32 chars)
  ci.engine.name	WHARF_CI_ENGINE_NAME	string
  ci.engine.api	WHARF_CI_ENGINE_API	string
  ci.engine.url	WHARF_CI_ENGINE_URL	string
  ci.engine.token	WHARF_CI_ENGINE_TOKEN	string
  ci.engine2.id	WHARF_CI_ENGINE2_ID	string (max 32 chars)
  ci.engine2.name	WHARF_CI_ENGINE2_NAME	string
  ci.engine2.api	WHARF_CI_ENGINE2_API	string
  ci.engine2.url	WHARF_CI_ENGINE2_URL	string
  ci.engine2.token	WHARF_CI_ENGINE2_TOKEN	string

  The deprecated trigger configs are used as defaults for the ci.engine.url and ci.engine.token configs.

• Added endpoint GET /api/engine for listing execution engines. (#134, #140)

• Added query parameter ?engine=ID to POST /api/project/{projectId}/build to allow specifying which execution engine to use for the new build. (#134)

• Added gRPC server (on the same port) for injecting logs in a single stream. See api/wharfapi/v5/builds.proto for full documentation of the API. (#147)

• Added build field workerId that is automatically populated if the engine API is wharf-cmd.v1. (#156)

• Added granular migrations support. Thanks to this, wharf-api now initializes much quicker as it can skip applying migrations that are already applied. (#144)

• Added automatic JSON indentation in HTTP responses based on the user agent, if they are a desktop, mobile, or tablet device, or specifically cURL. Can be disabled by the new query parameter ?pretty=false. (#158)

• Changed query parameter ?status and ?statusId in GET /api/build to support multiple values, where it will respond with builds matching any of the supplied statuses. (#150)

• Changed database column name token.token to token.value due to a bug in the Sqlite database driver. The HTTP response model still uses the field name "token". (#144)

• Added dependencies:

  • github.com/alta/protopatch v0.5.0 (#147)
  • github.com/go-gormigrate/gormigrate/v2 v2.0.0 (#144)
  • github.com/mileusna/useragent v1.0.2 (#158)
  • github.com/soheilhy/cmux v0.1.5 (#147)
  • google.golang.org/grpc v1.44.0 (#147)
  • google.golang.org/protobuf v1.27.1 (#147)

• Changed version of numerous dependencies:

  • github.com/gin-gonic/gin from v1.7.4 to v1.7.7 (#151)
  • github.com/swaggo/gin-swagger from v1.3.1 to v1.4.1 (#151)
  • github.com/swaggo/swag from v1.7.1 to v1.8.0 (#151)
  • gorm.io/driver/postgres from v1.1.1 to v1.2.3 (#144)
  • gorm.io/driver/sqlite from v1.1.5 to v1.2.6 (#144)
  • gorm.io/gorm from v1.21.15 to v1.22.5 (#144)

• Changed Go runtime from v1.16 to v1.17. (#148)

• Fixed testResultListSummary, testResultSummary and params not filled when fetching list of builds. (#131)

v5.0.0 wharf-api

Major version bump! We have decided to rewrite and redesign a lot of the REST API. We have kept the old endpoints from v4 for compatilibty so that the wharf-api-client-go v1 still works fine with wharf-api v5, for the most part. Check the changelog below for more info.

Docker image

Hosted over at https://quay.io/repository/iver-wharf/wharf-api

docker pull quay.io/iver-wharf/wharf-api:v5.0.0

RFCs implemented

Now includes implementation for the following Wharf RFCs:

• RFC-0013: authentication & authorization (iver-wharf/rfcs#13)
• RFC-0014: rework-handling-of-test-results (iver-wharf/rfcs#14)
• RFC-0016: wharf-api-endpoints-cleanup (iver-wharf/rfcs#16)
• RFC-0024: Project overrides (iver-wharf/rfcs#24)
• RFC-0026: v2+ Go modules release (iver-wharf/rfcs#26)

Changes (since v4.2.0)

• BREAKING: Changed module path from github.com/iver-wharf/wharf-api to github.com/iver-wharf/wharf-api/v5. (#128)

• BREAKING: Removed all deprecated environment variable configs, which were marked as deprecated in v4.2.0/#38. Now all environment variables require the WHARF_ prefix. (#87)

• BREAKING: Changed the following POST creation endpoints to solely create, instead of the previous behavior where it instead could update if it found an existing database object that matched the HTTP request data: (#88, #93)

  • POST /project
  • POST /provider
  • POST /token

• BREAKING: Removed RabbitMQ integration. All mq.* YAML configs and WHARF_MQ_* environment variables are no longer relevant. This may be implemented again later, but inside a new "notification" component instead of directly inside wharf-api. (#102)

• Deprecated PUT endpoints that took the object ID from the HTTP request body. They are still supported, but may be removed in the next major release (v6.0.0). Please refer to the new endpoints that takes the ID from the URL path. (#88, #91, #94, #97, #113)

  • Use PUT /project/{projectId} instead of PUT /project
  • Use PUT /provider/{providerId} instead of PUT /provider
  • Use PUT /token/{tokenId} instead of PUT /token
  • Use PUT /project/{projectId}/branch instead of PUT /branches

• Deprecated POST search endpoints that took the search queries from the HTTP request body. They are still supported, but may be removed in the next major release (v6.0.0). Please refer to the new endpoints that use query parameter instead. (#99, #109, #118, #119, #123)

  • Use new GET /project instead of GET /projects or POST /projects/search
  • Use new GET /build instead of GET /projects/{projectId}/builds or POST /builds/search
  • Use new GET /provider instead of GET /providers or POST /providers/search
  • Use new GET /token instead of GET /tokens or POST /tokens/search
  • Use new GET /build/{buildId}/artifact instead of GET /build/{buildId}/artifacts

• Deprecated /branch and /branches endpoints in favor of new /project/{projectId}/branch endpoints. (#120, #121)

• Deprecated PUT /build/{buildId} in favor of new PUT /build/{buildId}/status endpoint. (#120, #121)

• Deprecated POST /project/{projectId}/{stage}/run in favor of new POST /project/{projectId}/build endpoint. (#120, #121)

• Added new GET endpoints to get list of objects (as mentioned in note above), with large set of query parameters. Major difference with their "plural" GET counterparts, they all return paginated results instead, as well as a "totalCount" field for the overall query.

  By default all these new endpoints use a default limit of 100, but this can be disabled by specifying ?limit=0. (#109, #118)

• Added configuration of specific origins for CORS via the environment variable WHARF_HTTP_CORS_ALLOWORIGINS or the YAML key http.cors.allowOrigins. This is to make sending Authorization headers possible. (#101)

• Added a slew of options for setting OIDC parameters (see WHARF_HTTP_OIDC_*) for JWT token verification. Upon setting WHARF_HTTP_OIDC_ENABLE=true a check will be enforced for requests sent to the api such that all requests not carrying a valid bearer token will fail.

• Added support for Sqlite. Default database driver is still Postgres.

  Note: wharf-api must be compiled with CGO_ENABLED=1 (which is the default for Go builds) but our Docker build is compiled with CGO_ENABLED=0. If you need Sqlite support in our Docker image, then please file a new issue over at https://github.com/iver-wharf/wharf-api/issues/new, and we will take a look at it. (#86)

• Added configuration for selecting database driver, environment variable WHARF_DB_DRIVER or the YAML key db.driver. Valid values: (#86)

  • postgres (default)
  • sqlite

• Added configuration for Sqlite file path, environment variable WHARF_DB_PATH or the YAML key db.path. Defaults to wharf-api.db. (#86)

• Added dependency on gorm.io/driver/sqlite. (#86)

• Added updatedAt and createdAt fields to the following models: (#111)

  • response.Artifact
  • response.Branch
  • response.Build
  • response.Project
  • response.Provider
  • response.TestResultDetail
  • response.TestResultSummary
  • response.Token

  Objects created and updated before this patch will have the value null, but will get a valid date on first update, such as on first refresh for a project.

• Fixed bug where unable to delete a Project without first deleting all child objects. (#64)

• Fixed where wharf-core logging for Gin debug and error messages were set up after they were initially used, leading to a mix of wharf-core and Gin formatted logs. (#63)

• Added database tables: (#43)

  • test_result_detail
  • test_result_summary

• Added test-result specific endpoints: (#43, #118)

  • POST /build/{buildid}/test-result

    This should be used instead of POST /build/{buildid}/artifact when uploading test result files.

  • GET /build/{buildid}/test-result/detail

  • GET /build/{buildid}/test-result/summary

  • GET /build/{buildid}/test-result/summary/{artifactId}

  • GET /build/{buildid}/test-result/summary/{artifactId}/detail

  • GET /build/{buildid}/test-result/list-summary

• Deprecated endpoint GET /build/{buildid}/tests-results.

  Use GET /build/{buildid}/test-result/list-summary instead. The response data is slightly different; it has additional properties, and does not have a status property. (#43, #77, #118)

• Changed format of all endpoint's path parameters from all lowercase to camelCase: (#76)

  • branchid -> branchId
  • projectid -> projectId
  • providerid -> providerId
  • tokenid -> tokenId
  • buildid -> buildId

  This affects the Swagger documentation, but has no behavioral implications.

• Deprecated endpoint GET /branch/{branchId}. Getting a single branch by its ID has not been shown to have any benefits. Please refer to the GET /project/{projectId} endpoint instead. (#75)

• Removed Provider.UploadURL and all references to it, as it was unused. (#82)

• Removed DB column provider.upload_url, as it was unused. (#82)

• Added TestResultListSummary field to Build database model. This allows you to avoid N+1 HTTP requests when listing builds to show test summaries. (#80)

• Changed to preload TestResultSummaries field of Build database model. (#80)

• Added packages for "Plain Old Go Objects", with finer-grained decoupling between database, HTTP request, and HTTP response models. The Swagger documentation is affected by this, and some unused fields have been removed from certain endpoints, such as the tokenId in POST /token. The new packages are: (#78, #83)

  • pkg/model/database
  • pkg/model/request
  • pkg/model/response

• Added more backend validation on some endpoints, such as enforcing name field to be set when creating a new project. (#83)

• Fixed PUT /token where it did not use the providerId value from the HTTP request body. It now sets the provider's token if the field is supplied and non-zero. (#78)

• Added Swagger operation IDs to all endpoints. This has no effect on the API's behavior, but affects code generators. (#79)

• Fixed bug where projects created using the deprecated PUT /project endpoint would have set a null ProviderID in the database. (#96)

• Added Swagger attribute minimum to all ID path parameters, response bodies, and request bodies, as we do not support negative values there. (#98)

• Changed a lot of database columns to be NOT NULL where wharf-api already didn't support null/nil values. Migration steps have been added so any potential null values will be changed to empty strings or zeroes. The updated columns are: (#100)

  • artifact.file_name
  • build_param.value
  • param.default_value
  • param.value
  • project.avatar_url
  • project.build_definition
  • project.description
  • project.git_url
  • project.group_name
  • test_result_summary.file_name
  • token.user_name

• Added new field RemoteProjectID to the project model. (#112)

• Added endpoints to allow setting manual overrides for a project. These overrides are used in responses from GET /project and other, as well as in build parameters for newly started builds. New endpoints: (#117, #127)

  • GET /project/{projectId}/override to get all overrides
  • `PUT /project...

v5.0.0-rc.1 wharf-api

⚠️ This is a release candidate (RC). Additional breaking changes may be added before real release.

Docker image

Hosted over at https://quay.io/repository/iver-wharf/wharf-api

docker pull quay.io/iver-wharf/wharf-api:v5.0.0-rc.1

Changes (Since v4.2.0)

• BREAKING: Removed all deprecated environment variable configs, which were
  marked as deprecated in v4.2.0/#38. Now all environment variables require the
  WHARF_ prefix. (#87)

• BREAKING: Changed the following POST creation endpoints to solely create,
  instead of the previous behavior where it instead could update if it found an
  existing database object that matched the HTTP request data: (#88, #93)

  • POST /project
  • POST /provider
  • POST /token

• BREAKING: Removed RabbitMQ integration. All mq.* YAML configs and
  WHARF_MQ_* environment variables are no longer relevant. This may be
  implemented again later, but inside a new "notification" component instead of
  directly inside wharf-api. (#102)

• Deprecated PUT endpoints that took the object ID from the HTTP request body.
  They are still supported, but may be removed in the next major release
  (v6.0.0). Please refer to the new endpoints that takes the ID from the URL
  path. (#88, #91, #94, #97, #113)

  • Use PUT /project/{projectId} instead of PUT /project
  • Use PUT /provider/{providerId} instead of PUT /provider
  • Use PUT /token/{tokenId} instead of PUT /token
  • Use PUT /project/{projectId}/branch instead of PUT /branches

• Deprecated POST search endpoints that took the search queries from the HTTP
  request body. They are still supported, but may be removed in the next major
  release (v6.0.0). Please refer to the new endpoints that use query parameter
  instead. (#99, #109)

  • Use new GET /project instead of GET /projects or POST /projects/search
  • Use new GET /build instead of GET /projects/{projectId}/builds or POST /builds/search
  • Use new GET /provider instead of GET /providers or POST /providers/search
  • Use new GET /token instead of GET /tokens or POST /tokens/search
  • Use new GET /build/{buildId}/artifact instead of GET /build/{buildId}/artifacts

• Added new GET endpoints to get list of objects (as mentioned in note above),
  with large set of query parameters. Major difference with their "plural"
  GET counterparts, they all return paginated results instead, as well as a
  "totalCount" field for the overall query.

  By default all these new endpoints use a default limit of 100, but this can
  be disabled by specifying ?limit=0. (#109, #118)

• Added configuration of specific origins for CORS via the environment variable
  WHARF_HTTP_CORS_ALLOWORIGINS or the YAML key http.cors.allowOrigins. This
  is to make sending Authorization headers possible. (#101)

• Added support for Sqlite. Default database driver is still Postgres.

  Note: wharf-api must be compiled with CGO_ENABLED=1 (which is the default
  for Go builds) but our Docker build is compiled with CGO_ENABLED=0. If you
  need Sqlite support in our Docker image, then please file a new issue over
  at https://github.com/iver-wharf/wharf-api/issues/new, and we will take a
  look at it. (#86)

• Added configuration for selecting database driver, environment variable
  WHARF_DB_DRIVER or the YAML key db.driver. Valid values: (#86)

  • postgres (default)
  • sqlite

• Added configuration for Sqlite file path, environment variable WHARF_DB_PATH
  or the YAML key db.path. Defaults to wharf-api.db. (#86)

• Added dependency on gorm.io/driver/sqlite. (#86)

• Added updatedAt and createdAt fields to the following models: (#111)

  • response.Artifact
  • response.Branch
  • response.Build
  • response.Project
  • response.Provider
  • response.TestResultDetail
  • response.TestResultSummary
  • response.Token

  Objects created and updated before this patch will have the value null, but
  will get a valid date on first update, such as on first refresh for a project.

• Fixed bug where unable to delete a Project without first deleting all child
  objects. (#64)

• Fixed where wharf-core logging for Gin debug and error messages were set up
  after they were initially used, leading to a mix of wharf-core and Gin
  formatted logs. (#63)

• Added database tables: (#43)

  • test_result_detail
  • test_result_summary

• Added test-result specific endpoints: (#43, #118)

  • POST /build/{buildid}/test-result

    This should be used instead of POST /build/{buildid}/artifact
    when uploading test result files.

  • GET /build/{buildid}/test-result/detail

  • GET /build/{buildid}/test-result/summary

  • GET /build/{buildid}/test-result/summary/{artifactId}

  • GET /build/{buildid}/test-result/summary/{artifactId}/detail

  • GET /build/{buildid}/test-result/list-summary

• Deprecated endpoint GET /build/{buildid}/tests-results.

  Use GET /build/{buildid}/test-result/list-summary instead. The response
  data is slightly different; it has additional properties, and does not have a
  status property. (#43, #77, #118)

• Changed format of all endpoint's path parameters from all lowercase to
  camelCase: (#76)

  • branchid -> branchId
  • projectid -> projectId
  • providerid -> providerId
  • tokenid -> tokenId
  • buildid -> buildId

  This affects the Swagger documentation, but has no behavioral implications.

• Deprecated endpoint GET /branch/{branchId}. Getting a single branch by its
  ID has not been shown to have any benefits. Please refer to the
  GET /project/{projectId} endpoint instead. (#75)

• Removed Provider.UploadURL and all references to it, as it was unused. (#82)

• Removed DB column provider.upload_url, as it was unused. (#82)

• Added TestResultListSummary field to Build database model. This allows you
  to avoid N+1 HTTP requests when listing builds to show test summaries. (#80)

• Changed to preload TestResultSummaries field of Build database
  model. (#80)

• Added packages for "Plain Old Go Objects", with finer-grained decoupling
  between database, HTTP request, and HTTP response models.
  The Swagger documentation is affected by this, and some unused fields have
  been removed from certain endpoints, such as the tokenId in POST /token.
  The new packages are: (#78, #83)

  • pkg/model/database
  • pkg/model/request
  • pkg/model/response

• Added more backend validation on some endpoints, such as enforcing name
  field to be set when creating a new project. (#83)

• Fixed PUT /token where it did not use the providerId value from the HTTP
  request body. It now sets the provider's token if the field is supplied and
  non-zero. (#78)

• Added Swagger operation IDs to all endpoints. This has no effect on the API's
  behavior, but affects code generators. (#79)

• Fixed bug where projects created using the deprecated PUT /project endpoint
  would have set a null ProviderID in the database. (#96)

• Added Swagger attribute minimum to all ID path parameters, response bodies,
  and request bodies, as we do not support negative values there. (#98)

• Changed a lot of database columns to be NOT NULL where wharf-api already
  didn't support null/nil values. Migration steps have been added so any
  potential null values will be changed to empty strings or zeroes.
  The updated columns are: (#100)

  • artifact.file_name
  • build_param.value
  • param.default_value
  • param.value
  • project.avatar_url
  • project.build_definition
  • project.description
  • project.git_url
  • project.group_name
  • test_result_summary.file_name
  • token.user_name

• Added new field RemoteProjectID to the project model. (#112)

v4.2.0 wharf-api

Docker image

Hosted over at https://quay.io/repository/iver-wharf/wharf-api

docker pull quay.io/iver-wharf/wharf-api:v4.2.0

Changes (since v4.1.1)

• Added support for the TZ environment variable (setting timezones ex. "Europe/Stockholm") through the tzdata package. (#40)

• Added config loading from YAML files using github.com/iver-wharf/wharf-core/pkg/config together with new config models for configuring wharf-api. See config.go or the reference documentation on the Config type for information on how to configure wharf-api. (#38, #51)

• Deprecated all environment variable configs. They are still supported, but may be removed in the next major release (v5.0.0). Please refer to the new config schema seen in config.go and config_example_test.go. (#38)

• Added Makefile to simplify building and developing the project locally. (#41, #42)

• Added wharf-core logging for Gin debug and errors logging. (#45)

• Added wharf-core logging for GORM debug logging. (#45)

• Changed version of github.com/iver-wharf/wharf-core from v1.0.0 to v1.2.0. (#45, #52)

• Added documentation to the remaining types in the project. No more linting errors! (#46, #54)

• Added new endpoints /api/ping and /api/health. (#44)

• Deprecated / and /health endpoints, soon to be moved to /api/ping and /api/health respectively, so they are aligned with the current Swagger documentation. (#44)

• Changed logging and moved the httputils package to stay consistent with the provider API repos. (#47)

• Changed version of github.com/swaggo/swag/cmd/swag from v1.7.0 to v1.7.1 in Dockerfile and Makefile. (#48)

• Changed logging on "attempting to reach database" during initialization from "ERROR" to "WARN", and rephrased it a little. (#50)

• Fixed so failed parsing of build status in the PUT /build/{buildid} and POST /build/{buildid}/log endpoints not silently ignore it and fallback to "Scheduling", but instead respond with appropriate problem responses. (#54)

• Removed constraint that project groups cannot be changed in the PUT /project endpoint. This deprecates the problem /prob/api/project/cannot-change-group. (#55)

• Removed dead/unused function getProjectGroupFromGitURL and type logBroadcaster. (#57)

• Removed internal/httputils, which was moved to github.com/iver-wharf/wharf-core/pkg/cacertutil. (#52)

• Changed version of Docker base images, relying on "latest" patch version:

  • Alpine: 3.14.0 -> 3.14 (#59)
  • Golang: 1.16.5 -> 1.16 (#59)

v4.1.1 wharf-api

Docker image

Hosted over at https://quay.io/repository/iver-wharf/wharf-api

docker pull quay.io/iver-wharf/wharf-api:v4.1.1

Changes (since v4.1.0)

• Changed version of Docker base images:

  • Alpine: 3.13.4 -> 3.14.0 (#31, #36)
  • Golang: 1.13.4 -> 1.16.5 (#36)

• Changed version of GORMv2 from v1.20.12 to v1.21.11. No major changes, but as
  a bug in GORM was fixed we could finally move to the latest version. (#34)

• Changed references to wharf-core pkg/problem and pkg/ginutil. (#33)

• Changed all logging via fmt.Print and sirupsen/logrus to instead use the new
  github.com/iver-wharf/wharf-core/pkg/logger. (#37)

• Removed dependency on github.com/sirupsen/logrus. (#37)

v4.1.0 wharf-api

Docker image

Hosted over at https://quay.io/repository/iver-wharf/wharf-api

docker pull quay.io/iver-wharf/wharf-api:v4.1.0

Changes

• Added endpoint PUT /provider as an idempotent way of creating a provider. (#28)

• Add endpoint PUT /token as an idempotent way of creating a token. (#26)

• Added environment var for setting bind address and port. (#29)

• Fixed missing failed field from main.TestsResults in GET /build/{buildid}/tests-results. (#25)