Date
1 - 6 of 6
CF CLI v6.23.0 Released Today
Nikolay Valchev
Thanks, so we expect it in a future API and CLI change.
Regards, Nikolay |
|
Nicholas Calugar
Hi Nikolay,
toggle quoted message
Show quoted text
Are you wanting to set different environment variables for task runs? If so, we plan on adding that back once we get environment variables correct for V3 apps. You can follow our V3-GA epic here: https://www.pivotaltracker.com/epic/show/3189929 Thanks, Nick -- Nicholas Calugar On January 1, 2017 at 1:13:20 AM, Koper, Dies (diesk(a)fast.au.fujitsu.com)
wrote: Hi Nikolay, All I know is that this feature was removed from the API back in Oct, so we didn't consider exposing it in the CLI. https://www.pivotaltracker.com/story/show/131642035 Nick, care to comment? Regards, Dies Koper Cloud Foundry Product Manager - CLI -----Original Message----- From: Nikolay Valchev [mailto:nvvalchev(a)gmail.com] Sent: Tuesday, December 27, 2016 9:36 PM To: cf-dev(a)lists.cloudfoundry.org Subject: [cf-dev] Re: CF CLI v6.23.0 Released Today Hi, What about the feature of changing app environment for a concrete task run scope. Is this still to be enabled in future or abandoned as idea? Nikolay |
|
Koper, Dies <diesk@...>
Hi Nikolay,
toggle quoted message
Show quoted text
All I know is that this feature was removed from the API back in Oct, so we didn't consider exposing it in the CLI. https://www.pivotaltracker.com/story/show/131642035 Nick, care to comment? Regards, Dies Koper Cloud Foundry Product Manager - CLI -----Original Message-----
From: Nikolay Valchev [mailto:nvvalchev(a)gmail.com] Sent: Tuesday, December 27, 2016 9:36 PM To: cf-dev(a)lists.cloudfoundry.org Subject: [cf-dev] Re: CF CLI v6.23.0 Released Today Hi, What about the feature of changing app environment for a concrete task run scope. Is this still to be enabled in future or abandoned as idea? Nikolay |
|
Nikolay Valchev
Hi,
What about the feature of changing app environment for a concrete task run scope. Is this still to be enabled in future or abandoned as idea? Nikolay |
|
Nikolay Valchev
Hi,
What about the feature of changing app environment for a concrete task run scope. Is this still to be enabled in future or abandoned as idea? Nikolay |
|
Koper, Dies <diesk@...>
The CF CLI team just cut 6.23.0. Binaries and link to release notes are available at:
https://github.com/cloudfoundry/cli#downloads This is the last release to bundle the deprecated loggregator consumer library, which is used to talk to the loggregator endpoint on CF releases before v212. In the next cf CLI release this library is scheduled to be removed; regardless of the CF release version targeted, the noaa library will be used to talk to the doppler endpoint. This endpoint was deemed stable around CF v203: if targeting an earlier CF release and experiencing issues with commands that interact with the loggregator (e.g. logs, push), please stay on this release of the cf CLI until your target CF is upgraded. One-off tasks This release introduces commands to run, terminate and list tasks, available from CF release v247 (CC API v3.0.0) onwards. A task is an application or script whose code is included as part of a deployed application, but runs independently in its own container. It can be used to perform one-off jobs, such as: * Migrating a database * Sending an email * Running a batch job * Running a data processing script Refer to the Running Tasks documentation<https://docs.cloudfoundry.org/devguide/using-tasks.html> for details. Creating users with external identity providers The create-user command has been enhanced to allow the creation of users mapped to users in an external identity provider, such as LDAP. (#822<https://github.com/cloudfoundry/cli/pull/822>) $ cf create-user j.smith(a)example.com --origin ldap # LDAP user CLI client id and secret no longer hard-coded The client id and secret used by the cf CLI for certain UAA requests are now stored in the local config.json file, making it possible to configure custom ids and secrets, for example to use long-lived tokens for scripts in CI environments. We're working on proper documentation. For now, refer to #919 (comment)<https://github.com/cloudfoundry/cli/issues/919#issuecomment-268699211>. Built with Golang 1.7.4 Golang 1.7.4 was released this month, addressing a vulnerability that could affect cf CLI users on Darwin with trust preferences for root certificates. See this announcement<https://groups.google.com/forum/#!topic/golang-nuts/9eqIHqaWvck> for details. Refactored commands We are in the process of creating a more consistent user experience; our goal is to standardize UI output. For example, warnings and errors will consistently be outputted to stderr instead of stdout. As we iterate through the list of commands, we are also focusing on improving performance and stability. List of improved commands in this release: * api * create-user * delete-org * delete-orphaned-routes * unbind-service * version Fixed regressions * 32 bit binaries of cf CLI 6.22.2 panic on 32 bit systems for commands that interact with loggregator (such as push) due to 64 bit-only code in the doppler library. (#991<https://github.com/cloudfoundry/cli/issues/991>) * Commands that interact with loggregator (such as push) could panic if the connection with the loggegrator was interrupted (e.g. in the case of a loggregator restart) due to an issue in retry logic. (#1019<https://github.com/cloudfoundry/cli/issues/1019>) Updated commands * create-security-group and update-security-group now include the new "description" field in the JSON example in their help pages. This field is accepted from CF release v238 (CC API v2.57.0) onwards. * push now treats values of environment variables specified in the app manifest as strings so big integers do not unintentionally get converted into (harder to read) scientific numbers. (#996<https://github.com/cloudfoundry/cli/issues/996>) * push no longer panics when loggregator restarts while collecting app logs. (#1019<https://github.com/cloudfoundry/cli/issues/1019>) * delete-space now takes an optional org parameter to allow deletion of a space without targeting it. (#957<https://github.com/cloudfoundry/cli/pull/957>) * unbind-service no longer fails with an error saying the app is not bound when unbinding a service that is bound to more than 50 apps. (#948<https://github.com/cloudfoundry/cli/issues/948>) * delete-orphaned-routes now deletes all orphaned routes instead of stopping after deleting 50, and no longer exits with return code 0 when an error occurs. (https://www.pivotaltracker.com/story/show/131127157, #978<https://github.com/cloudfoundry/cli/issues/978>) New & Updated Community Plugins * top v0.7.5: https://github.com/ECSTeam/cloudfoundry-top-plugin * Usage Report v1.4.1: https://github.com/krujos/usagereport-plugin * Blue-green-deploy v1.1.0: https://github.com/bluemixgaragelondon/cf-blue-green-deploy * docker-usage v1.0.3: https://github.com/ECSTeam/docker-usage * cf-download v1.2.0: https://github.com/ibmjstart/cf-download * buildpack-usage v1.0.0: https://github.com/ECSTeam/buildpack-usage Enjoy! Regards, Dies Koper Cloud Foundry Product Manager - CLI |
|