Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Dec 15, 2025

Documentation Update for INIT_CONFIG Environment Variable

  • Explore repository structure and locate existing self-hosted documentation
  • Review the deployment page at /content/en/cloud/self-hosted/deployment/
  • Add INIT_CONFIG environment variable documentation to deployment page
  • Review and update the planning guide with configuration planning section
  • Fix frontmatter structure in planning guide (moved content from frontmatter to body)
  • Validate Hugo build succeeds (requires maintainer validation)

Changes Made

1. Deployment Guide (/content/en/cloud/self-hosted/deployment/_index.md)

Added comprehensive Environment Variables section with INIT_CONFIG documentation:

  • Purpose: Pre-configure provider settings, automate setup, define custom configurations
  • Usage Examples:
    • Bash/shell environment variable export
    • Docker deployment with -e flag
    • Kubernetes deployment with env variables in manifest
  • Configuration Schema: Provider name and settings structure
  • Reference Link: Links to detailed provider-init.md in meshery-cloud repository

2. Planning Guide (/content/en/cloud/self-hosted/planning/_index.md)

Added Provider Configuration Planning section:

  • Configuration Strategy: Planning checklist for provider identity, initial settings, config management
  • INIT_CONFIG Benefits: Reproducible deployments, CI/CD integration, Infrastructure as Code
  • Important Considerations: Startup-only processing warning
  • Cross-reference: Links to deployment guide for detailed usage
  • Fixed: Corrected frontmatter structure - content now properly in body, not frontmatter

Documentation Principles Applied

  • Diátaxis Framework: Deployment guide follows "How-to" pattern; Planning guide follows "Explanation" pattern
  • Minimal Changes: Only added new sections, preserved all existing content
  • Professional Tone: Clear, concise, welcoming to technical audiences
  • Accessibility: Proper heading hierarchy, descriptive text, semantic structure
  • Hugo Compliance: Valid shortcodes, proper frontmatter, Markdown syntax
  • Cross-referencing: Links between planning and deployment guides for better navigation

References

Original prompt

This section details on the original issue you should resolve

<issue_title>[Docs] Update self-hosted deployment instructions with new</issue_title>
<issue_description>#### Current State
This page needs updated: https://docs.layer5.io/cloud/self-hosted/deployment/.

Maybe a new page needs to be added to the planning guide - https://docs.layer5.io/cloud/self-hosted/planning/

Desired State

Incorporate user-facing documentation about the purpose and use of the INIT_CONFIG environment variable. References:


Contributor Guide and Resources

Comments on the Issue (you are @copilot in this section)

Custom agent used: Diátaxis Documentation Expert
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

@netlify
Copy link

netlify bot commented Dec 15, 2025

Deploy Preview for bejewelled-pegasus-b0ce81 ready!

Name Link
🔨 Latest commit 8f443c7
🔍 Latest deploy log https://app.netlify.com/projects/bejewelled-pegasus-b0ce81/deploys/694087cdbcf00d0008a9d975
😎 Deploy Preview https://deploy-preview-879--bejewelled-pegasus-b0ce81.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@pontusringblom pontusringblom marked this pull request as ready for review December 15, 2025 21:49
Copilot AI review requested due to automatic review settings December 15, 2025 21:49
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

Copilot AI and others added 2 commits December 15, 2025 21:52
…ployment guide

Co-authored-by: pontusringblom <170570911+pontusringblom@users.noreply.github.com>
Co-authored-by: pontusringblom <170570911+pontusringblom@users.noreply.github.com>
Copilot AI changed the title [WIP] Update self-hosted deployment instructions with INIT_CONFIG details docs(cloud): add INIT_CONFIG environment variable documentation for self-hosted deployments Dec 15, 2025
Copilot AI requested a review from pontusringblom December 15, 2025 21:55
@leecalcote
Copy link
Member

@aabidsofi19, should serverbaseURL come under this section?

@@ -1,5 +1,32 @@
---
title: Planning Layer5 Cloud Deployment
title: Planning
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot don't change the title.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in commit 8f443c7. The title is now preserved as "Planning" and the frontmatter structure is correct.

Comment on lines 3 to 29

## Provider Configuration Planning

When planning your self-hosted Layer5 Cloud deployment, consider how you will initialize and configure your provider instance. The `INIT_CONFIG` environment variable enables you to automate provider configuration during deployment.

### Configuration Strategy

Before deploying, plan your configuration approach:

1. **Provider Identity**: Define your provider name and identification
2. **Initial Settings**: Determine which settings need to be configured at startup
3. **Configuration Management**: Decide how configuration will be managed (environment variables, secrets, config files)
4. **Update Strategy**: Plan for configuration updates and changes over time

### Using INIT_CONFIG for Automated Setup

The `INIT_CONFIG` environment variable allows you to pre-configure your provider during deployment, eliminating manual setup steps. This is particularly valuable for:

- **Reproducible Deployments**: Ensure consistent configuration across environments
- **CI/CD Integration**: Automate deployments with predefined configurations
- **Infrastructure as Code**: Manage provider configuration alongside your infrastructure

For detailed usage and examples, see the [Deployment Guide](/cloud/self-hosted/deployment/#init_config).

{{< alert type="warning" title="Important" >}}
Plan your INIT_CONFIG carefully as it is only processed during initial startup. Changes require redeployment or manual configuration updates.
{{< /alert >}} Layer5 Cloud Deployment
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should not be included in the frontmatter, but should be in the body, @copilot.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in commit 8f443c7. The Provider Configuration Planning section is now properly placed in the body after the frontmatter closes with ---.

Co-authored-by: pontusringblom <170570911+pontusringblom@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Docs] Update self-hosted deployment instructions with new

3 participants