June 20-22 Announcing HashiConf Europe full schedule: keynotes, sessions, labs & more Register Now
  • Infrastructure
    • terraform
    • packer
  • Networking
    • consul
  • Security
    • vault
    • boundary
  • Applications
    • nomad
    • waypoint
    • vagrant
  • HashiCorp Cloud Platform

    A fully managed platform to automate infrastructure on any cloud with HashiCorp products.

    • consul
    • terraform
    • vault
    • packerbeta
    Visit cloud.hashicorp.com
  • Overview
  • Tutorials
  • Docs
  • CLI
  • Plugins
  • Community
GitHub
Download
    • v0.8.x (latest)
    • v0.7.x
    • v0.6.x
    • v0.5.x
    • v0.4.x
    • v0.3.x
    • v0.2.x
    • v0.1.x
    • Overview
      • Overview
      • Helm
      • Heroku, Vercel, etc.
      • Kubernetes
  • Getting Started
    • Overview
    • Compatibility Promise
    • Protocol Version Table
    • Release Notifications
      • Overview
      • Upgrade to 0.2.0

    • Install
    • Externally Built Images
    • Building Container Images
    • Helm Deployment
    • YAML-Free Deployment
    • YAML Directory Deployment
    • Resource Status
    • ConfigMaps and Secrets

    • Overview
    • Git Integration
    • Remote Operations
    • Overview
    • Build
    • Deploy
    • Release
    • Hooks
    • Labels
    • Workspace and Label Scoping
    • Overview
      • Overview
      • Input Variables
      • External Data
      • artifact
      • deploy
      • entrypoint
      • labels
      • path
      • workspace
      • Overview
      • Full Reference
      • Templating
      • Overview
      • Expressions
      • JSON Syntax
    • app
    • build
    • config
    • deploy
    • hook
    • plugin
    • registry
    • release
    • runner
    • url
    • use
    • variable
  • URL Service
  • Logs
  • Exec
    • Overview
    • Dynamic Values
    • Files
    • Internal Values
    • Workspace and Label Scoping
    • Overview
      • Overview
      • OIDC
      • Overview
      • Maintenance
      • Production
      • Security
    • Express Server Install
    • Overview
    • Configuration
    • Profiles
    • On-Demand Runner
    • Additional Runners
  • Workspaces
  • Plugins
  • Triggers

    • Overview
      • Overview
      • Registering Plugin Components
      • Handling Configuration
      • Implementing the Builder Interface
      • Compiling the Plugin
      • Creating an Example Application
      • Testing the Plugin
    • Initializing the SDK
    • Passing Values Between Components
      • Overview
      • Authenticator
      • Configurable
      • ConfigurableNotify
      • Builder
      • Registry
      • Platform
      • ReleaseManager
      • Destroy
      • Status
      • Default Parameters
      • Overview
    • Overview
    • Disable
    • Overview
    • GitHub Actions
    • GitLab CI/CD
    • CircleCI
    • Jenkins
  • Troubleshooting
  • Glossary

    • Overview
    • Architecture
    • Operation Execution
  • Roadmap
Type '/' to Search

»url Stanza

Placementapp -> url

The url stanza configures the behavior of the URL service for the given application. This allows for certain applications to opt-out of automatic hostname registration with the URL service, opt-in, etc.

The url stanza is optional. If it is not specified, the default URL settings configured with the Waypoint server will be used. The "default settings" are the URL settings for the running Waypoint server. These settings determine if the URL service is enabled at all along with whether apps get a hostname by default.

If the URL service is not enabled on the server, then the settings specified here have no effect.

app "frontend" {
  build {
    # ...
  }

  deploy {
    # ...
  }

  release {
    # ...
  }

  url {
    auto_hostname = false
  }

}
app "frontend" {
  build {
    # ...
  }

  deploy {
    # ...
  }

  release {
    # ...
  }

  url {
    auto_hostname = false
  }

}

»Opt-Out and Opt-in

This stanza allows applications to opt-out or opt-in to automatic hostname registration with the URL service.

Hostname registration is what makes an app routable with the URL service. If an app has no registered hostname, it can't be routed to. The default value of whether an app gets a registered hostname is determined based on the server configuration.

»Opt-Out

To opt-out of hostname registration, specify auto_hostname = false:

app "frontend" {
  url {
    auto_hostname = false
  }
}
app "frontend" {
  url {
    auto_hostname = false
  }
}

If you're using the entrypoint, the entrypoint will still connect to the URL service, but routing will be disabled until a hostname is registered. There is no way currently to prevent the entrypoint from connecting to the URL service altogether.

»Opt-In

To opt-in to hostname registration, specify auto_hostname = true:

app "frontend" {
  url {
    auto_hostname = true
  }
}
app "frontend" {
  url {
    auto_hostname = true
  }
}

If the URL service is enabled on the server and the default behavior configured on the server is for apps to not have a hostname registered, this will opt the application in to getting a hostname by default.

»url Parameters

»Optional

  • auto_hostname (bool: <server configuration>) - Whether to automatically generate a hostname for the application (and deployments) with the URL service. If this is disabled, you can manually use the waypoint hostname CLI to manage hostnames. If this is not specified, the default setting set at the server level will be used.
github logoEdit this page

Using Waypoint

The best way to understand what Waypoint can enable for your projects is to give it a try.

Waypoint tutorials
Waypoint documentation
Tutorial

Get Started - Kubernetes

Build, deploy, and release applications to a Kubernetes cluster.

View
Tutorial

Introduction to Waypoint

Waypoint enables you to publish any application to any platform with a single file and a single command.

View

Waypoint is maintained by HashiCorp, Inc.

View Code of Conduct
DocumentationCLI ReferenceTutorialsIntegrations
All systems normal