Link11 WAAP
v5
v5
  • Link11 WAAP Documentation
  • Release Notes
  • Known Issues
  • User Guide
    • Introduction to Link11 WAAP
  • How Link11 WAAP Works
    • Traffic Filtering Process
    • Traffic Reporting and Analytics
    • Policy Mapping and Traffic Routing
    • Tagging
    • UI Overview and Common Elements
  • Console UI Walkthrough
    • Analytics
      • Dashboard
      • Events Log
    • Security
      • Global Filters
      • Flow Control Policies
      • Security Policies
      • Rate Limit Rules
      • ACL Profiles
      • Actions
      • Dynamic Rules
      • Quarantined
      • Content Filter
        • Content Filter Profiles
        • Content Filter Rules
    • Sites
      • Server Groups
      • Proxy Templates
      • Mobile Application Groups
      • Backend Services
      • Edge Functions
      • DNS Records
      • SSL
        • Load Balancers
        • Certificates
    • System
      • Interactive Challenge
      • SSO Configuration
      • Purge CDN Cache
      • Users Management
      • Security Alerts
      • Log Exporters
      • Version Control
      • System DB
      • Publish Changes
    • Account
  • Using the product
    • Best Practices
      • Saving and Publishing Your Changes
      • Enabling Passive Challenges
      • Understanding and Diagnosing Traffic Issues
    • How Do I...
      • Authenticate mobile app users
      • Ban, unban, and allowlist traffic sources
      • Bypass Link11 WAAP for loadtesting or other purposes
      • Configure a new path/section of a site
      • Control caching behavior
      • Enable GraphQL traffic
      • Enable mTLS (mutual TLS)
      • Protect sensitive information in logs and analytics
      • Quickly block an attacker
      • Redirect or block HTTP traffic
      • Run custom code
      • Set rate limits and exemptions
      • Stream event data to a SIEM solution or other destination
    • The Link11 WAAP API
      • Overview
      • Internal data structures
      • Using Swagger UI
      • Using curl
  • Reference Information
    • Acronyms
    • API
      • API access to traffic data
      • Types of namespaces
      • Namespace reference
        • ACL Profiles
        • Actions
        • Backend Services
        • Certificates
        • Configs
        • Content Filter Profiles
        • Content Filter Rules
        • Data queries
        • Dynamic Rules
        • Edge Functions
        • Flow Control Policies
        • Global Filters
        • Load Balancers
        • Log Exporters
        • Mobile Application Groups
        • Planets
        • Proxy Templates
        • Rate Limit Rules
        • Security Alerts
        • Security Policies
        • Server Groups
        • Tags
        • Tools
        • Users
    • Hostile Bot Detection / LWCSI
      • Environmental detection and browser verification
      • Client authentication
      • Biometric behavioral verification
    • HTTP Response Codes
    • Log Exporter Output
    • Pattern Matching Syntax
    • Query Filter Syntax and Best Practices
  • Support
Powered by GitBook
On this page
  • Publishing recent edits to the current configuration
  • Publishing a version after working with Version Control
  • Changing to a different commit

Was this helpful?

Export as PDF
  1. Console UI Walkthrough
  2. System

Publish Changes

PreviousSystem DBNextAccount

Last updated 1 month ago

Was this helpful?

This page pushes a selected system configuration to the proxy, and makes it active. This is necessary when:

  • Edits were recently made to the current configuration

  • Changing to a different system configuration on the page: either reverting to a previous version, or rolling forward to one that's different than the currently active one.

Publishing recent edits to the current configuration

Whenever you change the configuration of the Link11 WAAP platform, you must save your changes. This is done with the "Save" button, available at the top of many pages within the UI.

If you do not save your changes, they will be lost when you go to a different page within the user interface. You will not be prompted or asked to confirm the abandonment of your changes.

After saving the changes, you must publish them as well, to push the changes out to the cloud. This is done by coming to this page and selecting the "Publish" button.

When you first arrive on this page, the most recent commit is automatically selected, so it is the one that is published when the button is selected. The most recent commit will include all of the changes that were made and saved.

Publishing a version after working with Version Control

After working with Version Control, you must come to this page, select the desired Commit entry (hovering the cursor over an entry will show the Select button), and select the "Publish" button on the top right.

Changing to a different commit

To set the system to a different commit, follow these steps:

  2. The Commit list is a list of configurations, with the most recently edited version at the top. If you wish to publish your most recent edits, ensure that the top entry is selected. If instead you wish to revert to a previous entry, find it in the list and select it.

  3. Select the "Publish" button on the top right.

In version 5, the UI does not show which commit is the current published version. We plan to add this in a future version.

In the pulldown at the top left of the sidebar menu, ensure that the appropriate Target Bucket(s) are selected. (The list of buckets is maintained in the .)

System DB
Version Control