Skip to content

@vito vito released this May 16, 2019

🔗 feature, breaking

  • @ralekseenkov has implemented generic credential caching for all credential managers!

    This replaces the Vault-only caching functionality. To transition, you'll need to update the following flags.

    • --vault-cache is now --secret-cache-enabled

    • --vault-max-lease is now --secret-cache-duration

    As part of this change, credential managers now implement a simpler interface that will make it easier to look-up secrets in multiple paths.

    For more information, see Credential Management.

    To follow along with future planned improvements to credential management, check out concourse/rfcs#21.

🔗 fix, breaking

  • @stigtermichiel changed the short-flag for fly builds --team from -t from -n to make it consistent across fly. Consistency is key.

🔗 feature

🔗 feature

  • The web node can now be configured to enable audit logs, thanks to a PR by @loghen41!

    Auditing currently logs API calls to the default logger using flags to enable specific auditing groups.

🔗 feature

  • Like a phoenix from the ashes, the pipeline navigation sidebar has made its triumphant return. It was initially removed to focus our efforts on the dashboard as a navigation flow. We have concluded that one click is better than two.

    Expect more design/UX polish in future releases!

🔗 feature

  • @itsdalmo has introduced a new in_parallel step which can run steps in parallel with more control via additional config: limit which will limit the number of parallel steps, and fail_fast which will interrupt currently running steps and prevent scheduling pending steps.

    This sounds a lot like the aggregate step, only better in every way (e.g. it doesn't have a stupid name), so fly set-pipeline will now issue deprecation warnings for aggregate: usage.

🔗 feature

  • Added a tooltip to the pause toggle on the dashboard page and the pipeline page explaining why it might be disabled.

🔗 feature

  • @hprotzek added the ability to retain build logs for a specific time duration and/or build count. See build_log_retention for more details.

🔗 security

  • We have restricted the SSH MAC algorithms used by the web node to a more secure set, overriding the Go defaults which allow weaker algorithms.

🔗 feature

  • Concourse is now compatible with Credhub v2.x (except for 2.1 due to a bug)! CredHub v1.9.x is still supported, too.

🔗 feature

  • Added ability set a name for the Concourse cluster which will be displayed on the dashboard page by setting cluster-name flag.

🔗 feature

  • @cappyzawa added a new get-team subcommand to fly. It allows you to retrieve a single team's config.

🔗 feature

  • @rkoster added a new flag --external-garden-url to allow use of a separately-managed Garden server as a worker.

🔗 feature

  • @pivotal-kahin-ng added a way of retaining the build history of a job when renaming it, by updating the job name and specifying its old name as old_name. After the pipeline has been configured, the old_name field can be removed.

🔗 fix

  • We reduced the default concurrency settings for volume sweeping from 5 to 3 as a way of reducing the stress that volume deletion ends up putting on the system in some cases.

🔗 fix

  • @edtan fixed a panic caused by running concourse web without a --session-signing-key.

🔗 fix

  • The Concourse API now returns 401 Unauthorized when an expired/invalid token is used to access an endpoint which supports authenticated/unauthenticated views.

    Previously it would just return a 200 response with less data, as if you weren't logged in, which made the behavior somewhat ambiguous and made auto-relogin logic difficult to implement consistently.

🔗 fix

  • Fixed a bug with Dex CloudFoundry connector when the user is a member of many teams. Thanks to @daniellavoie!

🔗 fix

  • Fixed a bug where the user gets a "You are not authorized to view the details of this pipeline" while watching a build.

🔗 fix

  • Fixed a bug where aborting a started build prior to a web node re-attaching to it would result in an orphaned, still running, uncompleted build.

    Along the way, the general 'aborting' flow has been refactored and should fix up any oddities caused by aborting builds at...inopportune moments.

🔗 fix

  • fly prune-worker --all-stalled has been fixed to only return a warning if no stalled workers are found, instead of an error.

🔗 fix

  • concourse quickstart has been fixed to ignore the --worker-tsa-worker-private-key flag.

🔗 fix

🔗 fix

  • Multiple groups in the same pipeline can no longer use the same name. An error is now raised if attempted.

🔗 fix

  • Fixed a bug where fly execute --input would hang indefinitely after uploading the input directory as a consequence of the web node stopping.
Assets 14
You can’t perform that action at this time.