IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2025-02-25 18:45:20 -06:00
Code Issues Packages Projects Releases Wiki Activity

Fixes some of the links for the TACOS docs (#1862)

Browse Source 
Signed-off-by: Andrew Hayes <andrew.hayes@harness.io>
This commit is contained in:
Andrew Hayes 2024-07-29 10:06:30 +01:00 committed by GitHub
parent 884410e63a
commit d2b603c8b2
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/docs/language/modules/sources.mdx
View File

@ -95,7 +95,7 @@ community.
You can also use a
[private registry](../../internals/module-registry-protocol.mdx), either
via [TACOS](../../../intro/tacos.mdx) (TF Automation and Collaboration Software), or by running a custom
via [TACOS](../../intro/tacos.mdx) (TF Automation and Collaboration Software), or by running a custom
service that implements
[the module registry protocol](../../internals/module-registry-protocol.mdx).
@ -135,7 +135,7 @@ You can learn more about the registry at the
To access modules from a private registry, you may need to configure an access
token [in the CLI config](../../cli/config/config-file.mdx#credentials). Use the
same hostname as used in the module source string. For a private registry
within [TACOS](../../../intro/tacos.mdx) (TF Automation and Collaboration Software), use the same authentication token as you would
within [TACOS](../../intro/tacos.mdx) (TF Automation and Collaboration Software), use the same authentication token as you would
use with the API or command-line clients.
## GitHub

2
website/docs/language/modules/syntax.mdx
View File

@ -98,7 +98,7 @@ version that meets the constraint.
Version constraints are supported only for modules installed from a module
registry, such as the [Public OpenTofu Registry](https://registry.opentofu.org/)
or any [TACOS](../../../intro/tacos.mdx) (TF Automation and Collaboration Software) private modules registry.
or any [TACOS](../../intro/tacos.mdx) (TF Automation and Collaboration Software) private modules registry.
Other module sources can provide their own versioning mechanisms within the
source string itself, or might not support versions at all. In particular,
modules sourced from local file paths do not support `version`; since