From 984d1bed58ee0515c712c39eaab8c49294609a07 Mon Sep 17 00:00:00 2001 From: Lasim Date: Mon, 31 Mar 2025 17:53:03 +0200 Subject: [PATCH] fix(docs): update release configuration link and remove limitations section from service connections documentation --- docs/docker-to-iac/publishing-to-npm.md | 2 +- docs/docker-to-iac/service-connections.md | 6 ------ 2 files changed, 1 insertion(+), 7 deletions(-) diff --git a/docs/docker-to-iac/publishing-to-npm.md b/docs/docker-to-iac/publishing-to-npm.md index eada088..19fd727 100644 --- a/docs/docker-to-iac/publishing-to-npm.md +++ b/docs/docker-to-iac/publishing-to-npm.md @@ -5,7 +5,7 @@ menuTitle: Publishing to NPM # Publishing docker-to-iac module to NPM -We have created an organization @deploystack for NPM. Publishing in NPM happens automatically through `semantic-release`. Config: [https://github.com/deploystackio/docker-to-iac/blob/main/.github/workflows/release.yml](https://github.com/deploystackio/docker-to-iac/blob/main/.github/workflows/release.yml) +We have created an organization @deploystack for NPM. Publishing in NPM happens automatically through `semantic-release`. Config: [https://github.com/deploystackio/docker-to-iac/blob/main/.github/workflows/release-pr.yml](https://github.com/deploystackio/docker-to-iac/blob/main/.github/workflows/release-pr.yml) The prerequisite for a release is a successful pull request to the default branch `main`. This means that all tests must first be successfully completed. `semantic-release` creates a new version and automatically publishes the node package to: [https://www.npmjs.com/package/@deploystack/docker-to-iac](https://www.npmjs.com/package/@deploystack/docker-to-iac) diff --git a/docs/docker-to-iac/service-connections.md b/docs/docker-to-iac/service-connections.md index 3fcbf5b..b91adb5 100644 --- a/docs/docker-to-iac/service-connections.md +++ b/docs/docker-to-iac/service-connections.md @@ -157,12 +157,6 @@ const serviceConnections = { // For Render - Will use fromService syntax instead of string replacement ``` -## Limitations - -- For Render.com, the module uses the `hostport` property which includes both hostname and port -- The feature only transforms environment variables specifically mentioned in the configuration -- Complex connection strings with multiple service references need each reference defined separately - ## Response Format The `translate` function returns information about the resolved service connections: