The new Waypoint 0.5 focuses on visibility around your application deployments and introduces governance for teams to enable better traceability.
We are pleased to announce the general availability of HashiCorp Waypoint 0.5. Waypoint is a tool that enables developers to describe how to get their applications from development to production in a single file and deploy using a single command, providing a modern workflow to build, deploy, and release across platforms.
Waypoint 0.5 focuses on improving visibility into the health of deployments while empowering teams to perform more actions in the Waypoint UI. You can view a breakdown of deployment resources, such as Kubernetes Services and their current health status, from the CLI and UI.
This release includes several key features and improvements:
waypoint.hclfile. Input variables enable platform operators to abstract details from the development team and create reusable Waypoint configurations.
This release includes many additional new features, workflow enhancements, general improvements, and bug fixes. The Waypoint 0.5 changelog contains a detailed list of all changes in this release.
Waypoint can now track the real-time health status of physical resources created as part of its operations, such as individual Kubernetes pods, Docker containers, AWS load balancers, and more. You can access the health status in both the UI and CLI.
In the Waypoint UI, you can refresh your application status with the click of a button. If you’re curious about how an application is doing and want an up-to-date report from the application platform, clicking the "Re-run health check" icon will regenerate a status report and update it for you on demand. Currently, this feature is limited to projects configured with a remote Git data source.
Before 0.5, even though a Waypoint deployment might declare itself as "successful," the deployed resources such as a Kubernetes pod could have failed after being created. Waypoint’s new status reports allow teams to determine the health of deployed resources.
For projects backed by a remote data source with Git, Waypoint server will automatically schedule a status report refresh for every application inside a project. By default, the server will refresh a project's application status at 5-minute intervals. You can adjust the refresh interval using the
waypoint project apply command or disable it per project.
A new CLI command has been introduced in this release:
waypoint status. This command provides details on the current state of all projects, their applications, and their applications’ deployment and release resources.
When you run
waypoint status inside a project directory, the new command will give you a quick overview of every application inside that project. This command includes a deployment’s workspace definition and the most recent deployment or release status check. Additionally, passing a target ‘project’ — such as
waypoint status project-name — will show you details of the project requested without having to save the project locally.
For a more detailed view of an application in a project, you can use the
-app flag for diving deeper. This view shows you an application summary, the summary of the last deployment, and its resources. If a release exists, the status command will also show you a release summary with the resources it created.
For a higher-level detail view of all projects defined inside your Waypoint server, you can run the
waypoint status command outside a project directory or include the
Along with the previously mentioned status report, the browser UI now presents an application’s operational status along with its health status, in a readable and transparent way:
The browser UI now displays complete deployment URLs instead of a more generic button label. Teams self-hosting URL services should find this feature particularly useful.
Projects that utilize the GitOps workflow within Waypoint now display the commit that triggered the operation, while clicking on the Git commit copies the Secure Hash Algorithm (SHA) value to your clipboard.
Input variables allow the customization of aspects of Waypoint configuration with values that may change or get set per Waypoint run. Users can now apply parameters by declaring variables in the
waypoint.hcl file and setting their values using CLI options, environment variables, and the Waypoint server UI.
By defining values that you can customize, you can provide a consistent interface to change how a given configuration behaves, allowing for easier cross-environment deployments. You can assign values to variables in different files — for example, a
test.wpvars and a
prod.wpvars — and then pull in those environment-specific values based on where you are releasing your deployment.
waypoint.hcl configuration file serves as a central location for variable definition, though values can originate from various sources based on your preferences for managing input values. Input variables make it easier to produce deployments across different workstreams, from developer workstations to your CI pipeline.
To give input variables a try, check out our HashiCorp Learn tutorial.
Before Waypoint 0.5, the only authentication method available was a token authentication mechanism including an invite capability to help facilitate token distribution. While Waypoint’s token system works well, the tokens don’t get assigned to an identity. That means individuals can use multiple tokens, making it impossible to determine who did what.
Waypoint now can support OIDC providers such as Google, GitLab, and others, though the OIDC functionality does not entirely replace the token system. The built-in token system supports machine-to-machine level access, and human operators can use OIDC to authenticate and acquire a token.
For more information on how to configure this feature, please refer to the OIDC documentation.
We hope you enjoy Waypoint 0.5!
If you’re attending AWS re:Invent in Las Vegas, Nov. 27 - Dec. 1, visit us for breakout sessions, expert talks, and product demos to learn how to accelerate your adoption of a cloud operating model.
From AI to the edge, HashiCorp Co-Founder and CTO Armon Dadgar shares his insights on where the cloud is headed, and what that means.
HashiConf 2023 unveils key announcements covering infrastructure and workflow enhancements as well as new security lifecycle management capabilities.