Change Log
Release Date: January 25, 2022
- [feature]
env sync
support for running via Velocity Operator - [feature]
env sync
can now build images remotely on the target cluster - [feature]
env sync
performance improvements - [feature]
env sync
support for syncing code into multiple pods - [feature]
env sync
support for running custom commands following code sync - [feature]
env sync
on command stop, the remote container will revert to the default blueprint image - [feature]
.velocity.yaml
updates to support new env sync features - [feature] When
.velocity.yaml
includes a single service, the-s
flag forveloctl
commands become optional. - [bug] When running
env portal
orenv develop
on a sleeping environment, a fail message will be shown if timeout is reached.
Release Date: Dec 27, 2022
- [feature] Added support for
env develop
when working withVelocityOperator
- [feature] A new command
operator enable-cloud-resources
enable cloud resources on a cluster managed byVelocityOperator
- [feature] A new command
veloctl operator install
to install or upgrade theVelocityOperator
Release Date: Dec 8, 2022
- [feature] Support for creating and updating environments from a partial k8s blueprint file:
env create -f <file> --source <source_name>
creates a new environment from a k8s blueprint file associated with the specified source while adding missing resources from the published blueprint stored in Velocity.env update -f <file> --source <source_name>
updates an existing environment from the k8s blueprint file associated with the specified source while keeping other resources deployed in the environment untouched.- [breaking change] Please note that this change breaks the existing default behavior. To bypass merging the configuration, use the
--override
flag. - [improvement]
snapshot download
was revised to provide better usability for k8s blueprints.- [breaking change] Please note that snapshot download will only be available for k8s blueprints. If you are using an older blueprint, contact Velocity for instructions on how to download snapshots from your account.
Release Date: Nov 27, 2022
- [Improvement] Improved error messages when
env create
fails due to cloud resource limitations - [Improvement] Improved error messages when
env develop
fails due to port conflicts - [feature]
env create --group
allows creating environments from predefined groups of services. Custom groups can be defined in the account setting dashboard https://app.velocity.tech/settings. - [bug] The CLI timeout was increased to allow the creation of environments that take longer to provision.
- [feature]
blueprint commit --source
associates all the committed resources to the specified source to allow replacing the resources on future commits. - [bug] stability improvements in
env sync
Release Date: Sep 20, 2022
- [bug]
veloctl status
Presents the process ID of the running portal in the Active Development Session table. This bug also affects the start/stop portal button of the Velocity JetBrains IDE Extension. - [feature]
blueprint commit
Stores and manages a persistent blueprint that is used when runningenv create -s
- [feature]
--template
flag forenv create
Outputs the k8s resources that will be applied to the cluster when creating the environment. Used for blueprint development and validation.
*Users of the JetBrains IDE Extension: It is recommended that you upgrade your CLI to v.0.5.6.
Release Date: Aug 22, 2022
[bug]
env portal
will not return an unexpected error when creating tunnelsRelease Date: Aug 1, 2022
- [feature]
env create -f
supports remote files. For example:veloctl env create -f HTTP://url/file.yaml
- [feature] Improved error messages for invalid k8s blueprints
- [feature] Additional output formats are now available for the
list-services
using a new--output
flag. - Generic bug fixes and stability improvements.
Release Date: Jul 28, 2022
- [bug fix]
env portal connect
will open tunnels to remote services as expected. - [feature] Additional output formats are now available for the
status
,env list
andenv status
commands using a new--output
flag.`
Release Date: Jul 25, 2022
- [feature] Additional commands were added to
veloctl snapshot
veloctl snapshot delete
Deletes an uploaded snapshotveloctl snapshot download
Downloads an uploaded snapshot
- [feature] A new flag:
--randomize-used-ports
was added toenv develop
andenv portal connect
to support running the commands using a random port when the target port is used. - [feature]
veloctl env create --all
will require a confirmation from the user to prevent unintentional creation of large environments. Using--confirm
can skip this confirmation. - [bug fix] Environment variables are not duplicated in the env file when using .veloctl.yaml
- [bug fix] Github ‘Create’ action will not fail the environment if a service blueprint contains special characters
Release Date: Jun 22, 2022
- [bug fix]
env up
veloct-bridge published ports are now kept the same as defined in the docker-compose file. - [bug fix]
env up
env list is available and enables running multiple docker compose environments.
Release Date: Jun 21, 2022
- [feature]
env create --param
controls the environment provisioning using predefined blueprint parameters. Read more: https://docs.velocity.tech/cli-guides/environment-parameters - [bug fix]
env portal
includes an auto-healing mechanism to recover broken tunnels after OS sleep - [feature]
env sleep --ttl
andenv destroy --ttl
allow changing the environment lifecycle definitions - [bug fix]
env up
local ports are now opened and allow connecting to local containers from an IDE
Release Date: May 22, 2022
- Usability improvements for
env sync
:- [feature] env sync can now take input parameters from a .velocity.yaml file to simplify the user experience. For more information: https://docs.velocity.tech/guides/using-a-velocity-configuration-file-.velocity.yaml
- [feature] env sync automatically ignores folders specified in .gitignore files
- [feature] Errors are now better highlighted, they provide more information and are surfaced earlier when possible
- [feature] A new file-sync infrastructure was implemented to enable Mac OS users to sync large folders
- More information about working with env sync: https://docs.velocity.tech/guides/sync-code-files-with-a-remote-environment
- Removing services from a running environment
- [feature]
env update -s <service name> --remove
will remove services from a running environment and help reduce infrastructure consumption. (Please note that services cannot be removed while other services depend on them
- Better usability for
env develop
:- [feature] env develop by default will print out indicative messages that explain how it works. To disable the messages and preserve a clean output, you can use -q or —quiet flag.
- Hybrid development environments from a Docker Compose file:
- [improvement]
env up
can now accept —local flag that indicates which services from the Docker Compose file should run locally, while all others are automatically offloaded to the remote cluster.
- In addition, v.0.4.7 includes general bug fixes and improved stability.
Release Date: Apr 19, 2022
- [beta release]
env up
andenv down
- Create and destroy hybrid development environments from a Docker Compose blueprint file. Read More: https://docs.velocity.tech/development-environment/overview - [feature]
env create
prints out a link to an Environment Dashboard: a web interface that presents information about the running environment. - [feature]
env develop
can now take input parameters from a .velocity.yaml file to simplify the user experience across team members - [Improvement] Better error messages when
env wakeup
fails.
Release Date: Mar 23, 2022
- [feature]
veloctl env create --all
is now available for creating a full environment with all available services - [feature] Improved troubleshooting
- Environments that failed as a result of a failing job will now print the failing job name in the error message
env logs
includes log messages of jobs running in the environment (for example database seeding jobs)env logs
is now more stable
- [bug fix] An unexpected server error when running
env sync
was fixed - [bug fix] Environments will not go to sleep while
env sync
is running
Release Date: Mar 8, 2022
- [improvement]
env portal connect
prints the connection details to the command output - [improvement] The environment status is displayed when
env wakeup
fails - [bug fix]
env status
does not return nil reference exception - [bug fix]
env develop --attach
does not return an error when attaching the same service twice - [bug fix] Environments will not go to sleep while
env logs
is running - [bug fix] Closing a running
env portal
while a service is attached detaches the service automatically
Release Date: Feb 23, 2022
- [new]
env describe
- A new command that provides detailed information of a running environment, including details of managed cloud services and databases. - [new]
env portal connect
is a new feature that creates a tunnel from your local machine to a remote container - [beta]
env sync
- A new command that synchronizes local file changes with a running container to enable hot reload. This command is in beta and is enabled upon request. - [bug fix]
env portal
is now closing all tunnels and cleaning up the --env-file upon exit - [bug fix] There is no delay when existing commands that were executed with the —help flag
- [bug fix] A clear error message is displayed when there is no internet connection
- [bug fix]
env logs
can now tail new logs upon execution
Release Date: Jan 25, 2022
- [Improvement]
env develop
andenv portal
are more stable and don’t hang after failed attach commands - [Improvement] When
env develop
fails due to port conflicts, it will instruct the user on how to resolve the issue - [Bug Fix]
env develop
doesn’t fail when running the same attach command in different terminal windows - [Bug Fix] The Windows download link was updated
Release Date: Jan 11, 2022
- [Improvement] Support for sharing the same NFS mount between different services in the same environment
- [Improvement] Improved performance for the
env develop
command env portal
is now compatible with the Windows operating system.env develop --service
filters out services that are not part of the selected environment.env list
is now faster and more stable.
Release Date: Dec 22, 2021
- [New Feature]
env portal
can be used as a single long-running process for tunneling to your environment. Seeenv develop --attach
for additional information on how to develop your service without runningenv develop
every time - [New Feature] The CLI will let you know when a new CLI version is available and how to install it.
- [New Feature] The
env sleep
andenv wakeup
commands are used to explicitly shut down environments (without data loss) and bring them up again.env develop
still automatically “wakes up” sleepy environments, so you don’t have to think about it beforehand. - [Enhancement] Tunneling and connection restoration are more robust.
- [Enhancement]
env create
now receives a--creator
flag to customize the environment creator name (in cases such as during CI).
Release Date: Nov 23, 2021
- [Enhancement]
veloctl
returns non-zero exit code when errors occur (such as “failed to create an environment”) - [Enhancement]
env logs
now writes only tostdout
- [Enhancement] Environment status now shows much more information when there’s a failure.
- [Enhancement] “Public URI”s of Ready services will now show during create/update (even before the environment is fully ready).
- [Bug Fix] When using
env develop
the CLI will not fail if the listening port is unavailable (no moreTimed out waiting for the service's port to become available.
errors). - [Bug Fix] Interrupts (<CMD>+C /<CTRL>+C) now work well within
env status
Release Date: Oct 28, 2021
- [Enhancement]
env logs
- See logs during environment creation or diagnose what failed. - [Enhancement] Environment status no longer clears the terminal.
- [Enhancement]
env list
displays only a number of the “dev candidates”, making the output clearer. - [Enhancement]
env create
shows lessenv develop
examples in environments with multiple services (making the output clearer here too!) - [Enhancement] Some errors display more detailed information.
- [Enhancement] Timestamps are now displayed in your local time zone.
- [Bug Fix] When
env develop
quits, there’s no longer an error.
Release Date: Oct 4, 2021
- [Enhancement]
env create
now supports—-confirm
when using image tags (e.g.,-s myservice:new-version
) - [Enhancement] Services list (during
env create
/env status
) now shows in alphabetic order - [Bug Fix] Running
veloctl
from CI no longer throws errors about missing directories (e.g., `~/.config`) - [Bug Fix] Occasional timeouts (“It took a bit too long to complete the command. Please try again.”)
[New Feature]
env update
- update an existing environment with the latest / custom plan- [Bug Fix] Running env develop on more than 2 services locally resulted in connection errors.
- [Bug Fix] Trying to run env develop locally on more than 12 services failed
Release Date: Aug 26, 2021
[Improvement] New environments now have their Creator displayed
[Bug Fix] env develop didn't work when the forwarded ports were bigger than 32767 (int16)
Release Date: Aug 17, 2021
- [Bug Fix] env create can read contents from standard input (--file -).
[Bug Fix] env create didn’t work when using the --file parameter.
- [Feature] Ability to enable users to easier set their environment snapshots via command flags when creating an environment.
- On env create, snapshots can be set using the repetitive flag --snapshot <service>=<snapshot-name>
- [Bug Fix] veloctl no longer displays errors after being upgraded via snap. (Linux.)
Release Date: July 20, 2021
- Google Pub/Sub - beta version is now available
- Bug Fixes:
- Assuming only one user works on a specific service, if veloctl is killed and the environment is “broken”, users can re-run env develop without an issue.
- Windows tunneling fix: env develop on Windows no longer has connection issues with external resources (e.g., databases).
You can check out our full documentation here including our getting started guides. The docs are frequently updated as we add new features or enhancements, so think of this as your continuous knowledge base of Velocity resources and tutorials.
Release Date: Jun 29, 2021
- To better understand your connectivity to the environment and the active debug sessions, you can leverage the new, veloctl status command, which will show the current state of all running session
Our TechDocs are now up so you can get step-by-step guides for using Velocity. We update them frequently whenever we add new features or enhancements.
Last modified 3mo ago