Skip to content

Commit

Permalink
Fixed non-html tags that fails rendering on docusaurus (cloudposse#546)
Browse files Browse the repository at this point in the history
Co-authored-by: Zinovii Dmytriv <[email protected]>
  • Loading branch information
zdmytriv and Zinovii Dmytriv authored Feb 3, 2023
1 parent 6fc46f9 commit 3391a43
Show file tree
Hide file tree
Showing 5 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -268,7 +268,7 @@ In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

## Copyright

Copyright © 2017-2022 [Cloud Posse, LLC](https://cpco.io/copyright)
Copyright © 2017-2023 [Cloud Posse, LLC](https://cpco.io/copyright)



Expand Down
4 changes: 2 additions & 2 deletions modules/datadog-agent/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ New Cluster Checks can be added to defaults to be applied in every account. Alte

Once they are added, and properly configured, the new checks show up in the network monitor creation under `ssl` and `Http`

**Please note:** the yaml file name doesn't matter, but the root key inside which is `something.yaml` does matter. this is following [datadogs docs](https://docs.datadoghq.com/agent/cluster_agent/clusterchecks/?tab=helm#configuration-from-static-configuration-files) for <integration name>.yaml.
**Please note:** the yaml file name doesn't matter, but the root key inside which is `something.yaml` does matter. this is following [datadogs docs](https://docs.datadoghq.com/agent/cluster_agent/clusterchecks/?tab=helm#configuration-from-static-configuration-files) for `<integration name>.yaml`.

## Monitoring Cluster Checks

Expand All @@ -89,7 +89,7 @@ https-checks:
HTTPS Check failed on <code>{{instance.name}}</code>
in Stage: <code>{{stage.name}}</code>
escalation_message: ""
tags:
tags:
managed-by: Terraform
notify_no_data: false
notify_audit: false
Expand Down
2 changes: 1 addition & 1 deletion modules/eks/external-dns/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,7 @@ components:
| <a name="input_tags"></a> [tags](#input\_tags) | Additional tags (e.g. `{'BusinessUnit': 'XYZ'}`).<br>Neither the tag keys nor the tag values will be modified by this module. | `map(string)` | `{}` | no |
| <a name="input_tenant"></a> [tenant](#input\_tenant) | ID element \_(Rarely used, not included by default)\_. A customer identifier, indicating who this instance of a resource is for | `string` | `null` | no |
| <a name="input_timeout"></a> [timeout](#input\_timeout) | Time in seconds to wait for any individual kubernetes operation (like Jobs for hooks). Defaults to `300` seconds | `number` | `null` | no |
| <a name="input_txt_prefix"></a> [txt\_prefix](#input\_txt\_prefix) | Prefix to create a TXT record with a name following the pattern prefix.<CNAME record>. | `string` | `"external-dns"` | no |
| <a name="input_txt_prefix"></a> [txt\_prefix](#input\_txt\_prefix) | Prefix to create a TXT record with a name following the pattern prefix.`<CNAME record>`. | `string` | `"external-dns"` | no |
| <a name="input_wait"></a> [wait](#input\_wait) | Will wait until all resources are in a ready state before marking the release as successful. It will wait for as long as `timeout`. Defaults to `true`. | `bool` | `null` | no |

## Outputs
Expand Down
2 changes: 1 addition & 1 deletion modules/eks/external-dns/variables.tf
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@ variable "chart_values" {
variable "txt_prefix" {
type = string
default = "external-dns"
description = "Prefix to create a TXT record with a name following the pattern prefix.<CNAME record>."
description = "Prefix to create a TXT record with a name following the pattern prefix.`<CNAME record>`."
}

variable "crd_enabled" {
Expand Down
2 changes: 1 addition & 1 deletion modules/zscaler/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ This parameter should be populated using `chamber`, which is included in the geo
chamber write zscaler key <value>
```

Where <value> is the ZScaler App Connector Provisioning Key. For more information on how to generate this key, see: [ZScaler documentation on Configuring App Connectors](https://help.zscaler.com/zpa/configuring-connectors).
Where `<value>` is the ZScaler App Connector Provisioning Key. For more information on how to generate this key, see: [ZScaler documentation on Configuring App Connectors](https://help.zscaler.com/zpa/configuring-connectors).

## Usage

Expand Down

0 comments on commit 3391a43

Please sign in to comment.