@@ -53,7 +53,7 @@ fast moving organizations. Opta is currently being used by dozens of companies o
To read more about the vision behind Opta, check out this [blog post](https://blog.runx.dev/infrastructure-as-code-for-everyone-7dad6b813cbc).
-If you'd like to try it out or have any questions - feel free to join our [Slack](https://slack.opta.dev/) or explore the [Getting Started Guide](http://run-x.gihub.io/getting-started)!
+If you'd like to try it out or have any questions - feel free to join our [Slack](https://slack.opta.dev/) or explore the [Getting Started Guide](http://run-x.github.io/getting-started)!
@@ -67,7 +67,7 @@ If you'd like to try it out or have any questions - feel free to join our [Slack
### Cloud services
Opta supports the 3 major clouds - AWS, GCP and Azure. It has modules for the most commonly used services in these clouds like:
-* Microservices (powered by [Kubernetes](http://run-x.gihub.io/architecture/aws/))
+* Microservices (powered by [Kubernetes](http://run-x.github.io/architecture/aws/))
* Databases - Postgres, MySQL, Redis
* Serverless workloads
* Networking - VPCs, Subnets, Load balancers
@@ -75,10 +75,10 @@ Opta supports the 3 major clouds - AWS, GCP and Azure. It has modules for the mo
* Object storage (S3, GCS)
Additionally, Opta has cloud and security best practices built in, including:
-* [Observability](http://run-x.gihub.io/features/observability/) (Datadog, LogDNA)
-* [SOC2 compliance](http://run-x.gihub.io/compliance/)
-* [Continuous Deployment](http://run-x.gihub.io/features/continuous_deployment/)
-* Hardened network and security configurations ([AWS](http://run-x.gihub.io/architecture/aws/), [GCP](http://run-x.gihub.io/architecture/gcp/), [Azure](http://run-x.gihub.io/architecture/azure))
+* [Observability](http://run-x.github.io/features/observability/) (Datadog, LogDNA)
+* [SOC2 compliance](http://run-x.github.io/compliance/)
+* [Continuous Deployment](http://run-x.github.io/features/continuous_deployment/)
+* Hardened network and security configurations ([AWS](http://run-x.github.io/architecture/aws/), [GCP](http://run-x.github.io/architecture/gcp/), [Azure](http://run-x.github.io/architecture/azure))
* Auto-scaling and high availability (HA)
@@ -86,13 +86,13 @@ Additionally, Opta has cloud and security best practices built in, including:
Opta aims to be compatible with your existing infrastructure setup. You can:
* Import existing Terraform infrastructure into Opta
-* Write [custom Terraform modules](http://run-x.gihub.io/reference/aws/modules/custom-terraform/) (for services that Opta doesn't support yet)
+* Write [custom Terraform modules](http://run-x.github.io/reference/aws/modules/custom-terraform/) (for services that Opta doesn't support yet)
* Run Opta in existing VPCs (WIP)
* Export the generated Terraform
# Try out Opta
-Check out the [Getting Started Guide](http://run-x.gihub.io/getting-started/).
+Check out the [Getting Started Guide](http://run-x.github.io/getting-started/).
You can also explore some [examples](https://github.com/run-x/opta/tree/main/examples) to get a better idea of what you can do with Opta.
diff --git a/UPGRADING.md b/UPGRADING.md
index b247fe5e6..54e6e3593 100644
--- a/UPGRADING.md
+++ b/UPGRADING.md
@@ -9,10 +9,10 @@ In some rare cases, upgrading an Opta version can cause a few minutes of downtim
## Upgrading Kubernetes version
### AWS
-Checkout our AWS EKS version upgrade guide [here](http://run-x.gihub.io/reference/aws/eks_upgrade/)
+Checkout our AWS EKS version upgrade guide [here](http://run-x.github.io/reference/aws/eks_upgrade/)
### GCP
-Checkout our GCP GKE version upgrade guide [here](http://run-x.gihub.io/reference/google/gke_upgrade/)
+Checkout our GCP GKE version upgrade guide [here](http://run-x.github.io/reference/google/gke_upgrade/)
## Upgrading database version
diff --git a/config/registry/aws/eks_upgrade.md b/config/registry/aws/eks_upgrade.md
index 3979c5a24..35f48ae5d 100644
--- a/config/registry/aws/eks_upgrade.md
+++ b/config/registry/aws/eks_upgrade.md
@@ -97,7 +97,7 @@ To do so, set the `k8s_version` field in the `k8s-cluster` block of your environ
**NOTE**: The `k8s_version` field may not be currently specified in your yaml as it comes with a default. Opta
continuously updates this default but in order to not force downtime on the users the changes in the default do not
-affect existing clusters, only new ones. Please refer to [here](http://run-x.gihub.io/reference/aws/modules/aws-eks/)
+affect existing clusters, only new ones. Please refer to [here](http://run-x.github.io/reference/aws/modules/aws-eks/)
for more details of the `k8s-cluster` block.
For example, if you just upgraded to kubernetes version 1.21, then your environment yaml may change from looking like
diff --git a/examples/README.md b/examples/README.md
index 5b8feb4b7..de2c7e5e5 100644
--- a/examples/README.md
+++ b/examples/README.md
@@ -1,6 +1,6 @@
# opta-examples
This directory holds a compiled list of advanced, standalone, usages of Opta, most beyond the basic tutorials on the
-[docs](http://run-x.gihub.io/)
+[docs](http://run-x.github.io/)
- [airflow](/examples/airflow): Deploy Apache Airflow on AWS
- [aws-lambda](/examples/aws-lambda): Deploy Apache Airflow on AWS
diff --git a/examples/byok-eks/README.md b/examples/byok-eks/README.md
index c74b9197c..9c653f30b 100644
--- a/examples/byok-eks/README.md
+++ b/examples/byok-eks/README.md
@@ -4,7 +4,7 @@ This is an example of using [Opta](https://github.com/run-x/opta) with an existi
# What does this do?
-This example provides Terraform files to configure Linkerd and Ingress Nginx controller in your EKS cluster to have the target [Network Architecture](http://run-x.gihub.io/features/networking/network_overview/).
+This example provides Terraform files to configure Linkerd and Ingress Nginx controller in your EKS cluster to have the target [Network Architecture](http://run-x.github.io/features/networking/network_overview/).
Once EKS is configured, you will be able to use Opta to deploy your service to Kubernetes.
Opta will generate the Terraform files and Helm chart for you, you only need to maintain the Opta file.
@@ -14,7 +14,7 @@ Opta will generate the Terraform files and Helm chart for you, you only need to
# When to use this instead of full Opta?
- Use this guide if you already have an EKS cluster, and would like to use Opta to deploy your Kubernetes services.
-- If you don't have an EKS cluser, Opta can create it, check [Getting Started](http://run-x.gihub.io/getting-started/) instead.
+- If you don't have an EKS cluser, Opta can create it, check [Getting Started](http://run-x.github.io/getting-started/) instead.
# What is included?
diff --git a/examples/flyte/flyte-aws.yaml b/examples/flyte/flyte-aws.yaml
index bf7fd1950..c452ba9cc 100644
--- a/examples/flyte/flyte-aws.yaml
+++ b/examples/flyte/flyte-aws.yaml
@@ -8,7 +8,7 @@ modules:
- type: base
- type: dns
domain: <>
- delegated: false # set to true once ready http://run-x.gihub.io/miscellaneous/ingress/
+ delegated: false # set to true once ready http://run-x.github.io/miscellaneous/ingress/
- type: k8s-cluster
max_nodes: 15
- type: k8s-base
diff --git a/examples/full-stack-example/README.md b/examples/full-stack-example/README.md
index 3ab66bdd2..02507d98d 100644
--- a/examples/full-stack-example/README.md
+++ b/examples/full-stack-example/README.md
@@ -127,7 +127,7 @@ opta destroy --config full-stack-example/providers/aws.yaml --auto-approve
# Further Reading
-Visit [Opta Documentation](http://run-x.gihub.io/) to learn more.
+Visit [Opta Documentation](http://run-x.github.io/) to learn more.
# Credits
diff --git a/examples/grpcbin/README.md b/examples/grpcbin/README.md
index 2db25de51..cf414834a 100644
--- a/examples/grpcbin/README.md
+++ b/examples/grpcbin/README.md
@@ -13,7 +13,7 @@ This directory contains:
└── grpcbin.yaml # opta service file
**NOTE**: Typically, the first step of the example would be to demonstrate how one may deploy the application locally
-but currently GRPC with opta does not function locally, and requires [TLS set up](http://run-x.gihub.io/tutorials/ingress/#setting-the-domain-for-an-environment-via-domain-delegation)
+but currently GRPC with opta does not function locally, and requires [TLS set up](http://run-x.github.io/tutorials/ingress/#setting-the-domain-for-an-environment-via-domain-delegation)
in the cloud environments to function. If you have pressing need for this feature, please let us know in our
[slack channel](https://slack.opta.dev)
@@ -33,7 +33,7 @@ in the cloud environments to function. If you have pressing need for this featur
# when done, find load_balancer_raw_dns or load_balancer_raw_ip in the output and save it
export load_balancer=[Value from output]
```
-3. Complete the [TLS and domain set up](http://run-x.gihub.io/tutorials/ingress/#setting-the-domain-for-an-environment-via-domain-delegation)
+3. Complete the [TLS and domain set up](http://run-x.github.io/tutorials/ingress/#setting-the-domain-for-an-environment-via-domain-delegation)
4. Deploy the service: push the image and deploy it to Kubernetes
```bash
opta apply --config grpcbin.yaml --auto-approve --env $ENV
diff --git a/examples/minecraft/README.md b/examples/minecraft/README.md
index f73f87e01..8bd3af8e3 100644
--- a/examples/minecraft/README.md
+++ b/examples/minecraft/README.md
@@ -37,7 +37,7 @@ this by modifying the `env_vars` field of the k8s-service module of the deployme
# Multiple Minecraft Servers
If you wish to host multiple minecraft servers/worlds in the same environment, do the following steps:
-* Create a new [Opta Service](http://run-x.gihub.io/getting-started/aws/#service-creation) yaml manifest holding a new
+* Create a new [Opta Service](http://run-x.github.io/getting-started/aws/#service-creation) yaml manifest holding a new
k8s-service module instance under the modules list (**WARNING**: this is needed because Opta currently only allows
one k8s service per yaml manifest).
* In your new service manifest, update the `service_port` field set to 25565 to a new value (typically just increment
@@ -105,7 +105,7 @@ name_servers = tolist([
* Your minecraft server should now be accessible under your domain-- go ahead and update your minecraft client config
to point to this new domain instead of the load balancer directly.
-For more information, checkout this [this tutorial](http://run-x.gihub.io/tutorials/ingress/) and follow the dns
+For more information, checkout this [this tutorial](http://run-x.github.io/tutorials/ingress/) and follow the dns
delegation steps.
# [FAQ](../FAQ.md)
diff --git a/examples/nocodb/nocodb-aws.yaml b/examples/nocodb/nocodb-aws.yaml
index c7a35c280..971369431 100644
--- a/examples/nocodb/nocodb-aws.yaml
+++ b/examples/nocodb/nocodb-aws.yaml
@@ -8,7 +8,7 @@ modules:
- type: base
- type: dns
domain: >
- delegated: false # set to true once ready http://run-x.gihub.io/miscellaneous/ingress/
+ delegated: false # set to true once ready http://run-x.github.io/miscellaneous/ingress/
- type: k8s-cluster
- type: k8s-base
name: k8sbase
diff --git a/examples/opta-mern-stack/README.md b/examples/opta-mern-stack/README.md
index 4e7b87728..f46dd330e 100644
--- a/examples/opta-mern-stack/README.md
+++ b/examples/opta-mern-stack/README.md
@@ -1,7 +1,7 @@
![alt text](MERN.jpg "MERN Stack MongoDB, Express, React, Node.js")
## Introduction
-MERN stack is a web software stack that includes MongoDB, Express.js, React, and Node.js. In this post we show how you can use [Opta](http://run-x.gihub.io/) to easily stand up a MERN-based application stack on a public cloud (aws) or Local development Kubernetes cluster. Specifically:
+MERN stack is a web software stack that includes MongoDB, Express.js, React, and Node.js. In this post we show how you can use [Opta](http://run-x.github.io/) to easily stand up a MERN-based application stack on a public cloud (aws) or Local development Kubernetes cluster. Specifically:
1. An [AWS eks/Local PC Kind] Kubernetes cluster built to SOC2 security standards
@@ -14,7 +14,7 @@ MERN stack is a web software stack that includes MongoDB, Express.js, React, and
## Pre-requisites
-Opta is a new kind of Infrastructure-As-Code framework where you work with high-level constructs instead of getting lost in low level cloud configuration or having to deal with [Terraform HCL](https://blog.runx.dev/my-pet-peeves-with-terraform-f9bb37d94950). You can install Opta on your PC by following the instructions [here](http://run-x.gihub.io/installation/).
+Opta is a new kind of Infrastructure-As-Code framework where you work with high-level constructs instead of getting lost in low level cloud configuration or having to deal with [Terraform HCL](https://blog.runx.dev/my-pet-peeves-with-terraform-f9bb37d94950). You can install Opta on your PC by following the instructions [here](http://run-x.github.io/installation/).
Our MERN stack example is based on the application code created by The MongoDB Atlas team. Their [blog post](https://www.mongodb.com/languages/mern-stack-tutorial) will walk you through the Nodejs+Express backend, React frontend and MongoDB code. You should take a moment to read the blog post, although keep in mind that most of the manual/click-on-GUI steps mentioned in the post to setup the infrastructure are not applicable to this Opta Infrastructure-as-code MERN stack example.
@@ -22,9 +22,9 @@ You can choose to deploy the MERN stack application on Kubernetes running in AWS
1. Clone the [Opta repo](https://github.com/run-x/opta); the MERN stack example is located in the `opta-mern-stack` sub-directory of the examples directory of this repository.
-2. Install Opta, as mentioned above, using [these instructions](http://run-x.gihub.io/installation/).
+2. Install Opta, as mentioned above, using [these instructions](http://run-x.github.io/installation/).
3. Make a MongoDB Atlas account and obtain their [API credentials](https://docs.atlas.mongodb.com/tutorial/manage-programmatic-access?utm_source=runx_opta&utm_campaign=pla&utm_medium=referral); you will need these in your terminal environment to allow Opta to spin up a MongoDB cluster for your application.
-4. If you don't already have your cloud credentials (AWS), you can follow the Opta instructions for [AWS](http://run-x.gihub.io/getting-started/aws/). If you plan on deploying with Opta [locally](http://run-x.gihub.io/getting-started/local/) on your PC, this step is not needed.
+4. If you don't already have your cloud credentials (AWS), you can follow the Opta instructions for [AWS](http://run-x.github.io/getting-started/aws/). If you plan on deploying with Opta [locally](http://run-x.github.io/getting-started/local/) on your PC, this step is not needed.
So as an example, for AWS, you will inject the API keys into your terminal environment where opta will be invoked like so
@@ -90,7 +90,7 @@ Click on the top left "MongoDB" image to see the list of records.
![alt text](mern-record-list.png "MERN Stack React SPA Record List")
-As a side note, you can always configure DNS and TLS certificates using Opta for your your production application, as explained [here](http://run-x.gihub.io/tutorials/ingress/).
+As a side note, you can always configure DNS and TLS certificates using Opta for your your production application, as explained [here](http://run-x.github.io/tutorials/ingress/).
## Teardown
diff --git a/modules/aws_k8s_service/aws-k8s-service.json b/modules/aws_k8s_service/aws-k8s-service.json
index 37cfe3823..5bdd80776 100644
--- a/modules/aws_k8s_service/aws-k8s-service.json
+++ b/modules/aws_k8s_service/aws-k8s-service.json
@@ -33,7 +33,7 @@
},
"healthcheck_command": {
"type": "array",
- "description": "See the See the [healthcheck probe](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `[]` (i.e., no user-specified healthchecks)",
+ "description": "See the See the [healthcheck probe](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `[]` (i.e., no user-specified healthchecks)",
"default": []
},
"liveness_probe_command": {
@@ -92,14 +92,14 @@
},
"autoscaling_target_cpu_percentage": {
"type": "integer",
- "description": "See the [autoscaling](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#autoscaling) section.",
+ "description": "See the [autoscaling](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#autoscaling) section.",
"default": 80,
"minimum": 0,
"maximum": 100
},
"autoscaling_target_mem_percentage": {
"type": "integer",
- "description": "See the [autoscaling](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#autoscaling) section.",
+ "description": "See the [autoscaling](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#autoscaling) section.",
"default": 80,
"minimum": 0,
"maximum": 100
@@ -119,7 +119,7 @@
},
"healthcheck_path": {
"type": "string",
- "description": "See the See the [healthcheck probe](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `null` (i.e., no user-specified healthchecks)"
+ "description": "See the See the [healthcheck probe](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `null` (i.e., no user-specified healthchecks)"
},
"liveness_probe_path": {
"type": "string",
@@ -154,7 +154,7 @@
"default": 86400
},
"resource_request": {
- "description": "See the [container resources](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#resource-requests) section.\nCPU is given in millicores, and Memory is in megabytes.\n",
+ "description": "See the [container resources](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#resource-requests) section.\nCPU is given in millicores, and Memory is in megabytes.\n",
"type": "object",
"properties": {
"cpu": {
diff --git a/modules/aws_k8s_service/aws-k8s-service.yaml b/modules/aws_k8s_service/aws-k8s-service.yaml
index 5106510d2..be8dc126c 100644
--- a/modules/aws_k8s_service/aws-k8s-service.yaml
+++ b/modules/aws_k8s_service/aws-k8s-service.yaml
@@ -76,12 +76,12 @@ inputs:
- name: autoscaling_target_cpu_percentage
user_facing: true
validator: any(str(), int(), required=False)
- description: See the [autoscaling](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#autoscaling) section.
+ description: See the [autoscaling](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#autoscaling) section.
default: 80
- name: autoscaling_target_mem_percentage
user_facing: true
validator: any(str(), int(), required=False)
- description: See the [autoscaling](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#autoscaling) section.
+ description: See the [autoscaling](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#autoscaling) section.
default: 80
- name: secrets
user_facing: true
@@ -101,12 +101,12 @@ inputs:
- name: healthcheck_path
user_facing: true
validator: str(required=False)
- description: See the See the [healthcheck probe](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `null` (i.e., no user-specified healthchecks)
+ description: See the See the [healthcheck probe](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `null` (i.e., no user-specified healthchecks)
default: null
- name: healthcheck_command
user_facing: true
validator: list(str(), required=False)
- description: See the See the [healthcheck probe](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `[]` (i.e., no user-specified healthchecks)
+ description: See the See the [healthcheck probe](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `[]` (i.e., no user-specified healthchecks)
default: []
- name: liveness_probe_command
user_facing: true
@@ -157,7 +157,7 @@ inputs:
user_facing: true
validator: any(include('resources'), required=False)
description: |
- See the [container resources](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#resource-requests) section.
+ See the [container resources](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#resource-requests) section.
CPU is given in millicores, and Memory is in megabytes.
default:
cpu: 100
diff --git a/modules/azure_k8s_service/azure-k8s-service.json b/modules/azure_k8s_service/azure-k8s-service.json
index a69526483..7110d1278 100644
--- a/modules/azure_k8s_service/azure-k8s-service.json
+++ b/modules/azure_k8s_service/azure-k8s-service.json
@@ -43,7 +43,7 @@
},
"healthcheck_command": {
"type": "array",
- "description": "See the See the [healthcheck probe](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `[]` (i.e., no user-specified healthchecks)",
+ "description": "See the See the [healthcheck probe](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `[]` (i.e., no user-specified healthchecks)",
"default": []
},
"liveness_probe_command": {
@@ -68,14 +68,14 @@
},
"autoscaling_target_cpu_percentage": {
"type": "integer",
- "description": "See the [autoscaling](http://run-x.gihub.io/reference/azurerm/modules/azure-k8s-service/#autoscaling) section.",
+ "description": "See the [autoscaling](http://run-x.github.io/reference/azurerm/modules/azure-k8s-service/#autoscaling) section.",
"default": 80,
"minimum": 0,
"maximum": 100
},
"autoscaling_target_mem_percentage": {
"type": "integer",
- "description": "See the [autoscaling](http://run-x.gihub.io/reference/azurerm/modules/azure-k8s-service/#autoscaling) section.",
+ "description": "See the [autoscaling](http://run-x.github.io/reference/azurerm/modules/azure-k8s-service/#autoscaling) section.",
"default": 80,
"minimum": 0,
"maximum": 100
@@ -95,7 +95,7 @@
},
"healthcheck_path": {
"type": "string",
- "description": "See the See the [healthcheck probe](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `null` (i.e., no user-specified healthchecks)"
+ "description": "See the See the [healthcheck probe](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `null` (i.e., no user-specified healthchecks)"
},
"liveness_probe_path": {
"type": "string",
@@ -130,7 +130,7 @@
"default": 86400
},
"resource_request": {
- "description": "See the [container resources](http://run-x.gihub.io/reference/azurerm/modules/azure-k8s-service/#container-resources) section.\nCPU is given in millicores, and Memory is in megabytes.\n",
+ "description": "See the [container resources](http://run-x.github.io/reference/azurerm/modules/azure-k8s-service/#container-resources) section.\nCPU is given in millicores, and Memory is in megabytes.\n",
"type": "object",
"properties": {
"cpu": {
diff --git a/modules/azure_k8s_service/azure-k8s-service.yaml b/modules/azure_k8s_service/azure-k8s-service.yaml
index a01dd6b49..68d498b63 100644
--- a/modules/azure_k8s_service/azure-k8s-service.yaml
+++ b/modules/azure_k8s_service/azure-k8s-service.yaml
@@ -62,12 +62,12 @@ inputs: # (what users see)
- name: autoscaling_target_cpu_percentage
user_facing: true
validator: any(str(), int(), required=False)
- description: See the [autoscaling](http://run-x.gihub.io/reference/azurerm/modules/azure-k8s-service/#autoscaling) section.
+ description: See the [autoscaling](http://run-x.github.io/reference/azurerm/modules/azure-k8s-service/#autoscaling) section.
default: 80
- name: autoscaling_target_mem_percentage
user_facing: true
validator: any(str(), int(), required=False)
- description: See the [autoscaling](http://run-x.gihub.io/reference/azurerm/modules/azure-k8s-service/#autoscaling) section.
+ description: See the [autoscaling](http://run-x.github.io/reference/azurerm/modules/azure-k8s-service/#autoscaling) section.
default: 80
- name: secrets
user_facing: true
@@ -87,12 +87,12 @@ inputs: # (what users see)
- name: healthcheck_path
user_facing: true
validator: str(required=False)
- description: See the See the [healthcheck probe](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `null` (i.e., no user-specified healthchecks)
+ description: See the See the [healthcheck probe](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `null` (i.e., no user-specified healthchecks)
default: null
- name: healthcheck_command
user_facing: true
validator: list(str(), required=False)
- description: See the See the [healthcheck probe](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `[]` (i.e., no user-specified healthchecks)
+ description: See the See the [healthcheck probe](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `[]` (i.e., no user-specified healthchecks)
default: []
- name: liveness_probe_command
user_facing: true
@@ -143,7 +143,7 @@ inputs: # (what users see)
user_facing: true
validator: any(include('resources'), required=False)
description: |
- See the [container resources](http://run-x.gihub.io/reference/azurerm/modules/azure-k8s-service/#container-resources) section.
+ See the [container resources](http://run-x.github.io/reference/azurerm/modules/azure-k8s-service/#container-resources) section.
CPU is given in millicores, and Memory is in megabytes.
default:
cpu: 100
diff --git a/modules/cloudfront_distribution/tf_module/main.tf b/modules/cloudfront_distribution/tf_module/main.tf
index c390eefea..9d0844f0c 100644
--- a/modules/cloudfront_distribution/tf_module/main.tf
+++ b/modules/cloudfront_distribution/tf_module/main.tf
@@ -14,7 +14,7 @@ data "aws_lb" "ingress-nginx" {
}
-# This is optional, see Opta docs for this here: http://run-x.gihub.io/reference/aws/modules/cloudfront-distribution/
+# This is optional, see Opta docs for this here: http://run-x.github.io/reference/aws/modules/cloudfront-distribution/
#tfsec:ignore:aws-cloudfront-enable-waf
resource "aws_cloudfront_distribution" "distribution" {
diff --git a/modules/gcp_k8s_service/gcp-k8s-service.json b/modules/gcp_k8s_service/gcp-k8s-service.json
index ad1396dea..9c46043ee 100644
--- a/modules/gcp_k8s_service/gcp-k8s-service.json
+++ b/modules/gcp_k8s_service/gcp-k8s-service.json
@@ -38,7 +38,7 @@
},
"healthcheck_command": {
"type": "array",
- "description": "See the See the [healthcheck probe](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `[]` (i.e., no user-specified healthchecks)",
+ "description": "See the See the [healthcheck probe](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `[]` (i.e., no user-specified healthchecks)",
"default": []
},
"liveness_probe_command": {
@@ -77,14 +77,14 @@
},
"autoscaling_target_cpu_percentage": {
"type": "integer",
- "description": "See the [autoscaling](http://run-x.gihub.io/reference/google/modules/gcp-k8s-service/#autoscaling) section.",
+ "description": "See the [autoscaling](http://run-x.github.io/reference/google/modules/gcp-k8s-service/#autoscaling) section.",
"default": 80,
"minimum": 0,
"maximum": 100
},
"autoscaling_target_mem_percentage": {
"type": "integer",
- "description": "See the [autoscaling](http://run-x.gihub.io/reference/google/modules/gcp-k8s-service/#autoscaling) section.",
+ "description": "See the [autoscaling](http://run-x.github.io/reference/google/modules/gcp-k8s-service/#autoscaling) section.",
"default": 80,
"minimum": 0,
"maximum": 100
@@ -104,7 +104,7 @@
},
"healthcheck_path": {
"type": "string",
- "description": "See the See the [healthcheck probe](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `null` (i.e., no user-specified healthchecks)"
+ "description": "See the See the [healthcheck probe](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `null` (i.e., no user-specified healthchecks)"
},
"liveness_probe_path": {
"type": "string",
@@ -139,7 +139,7 @@
"default": 86400
},
"resource_request": {
- "description": "See the [container resources](http://run-x.gihub.io/reference/google/modules/gcp-k8s-service/#container-resources) section.\nCPU is given in millicores, and Memory is in megabytes.\n",
+ "description": "See the [container resources](http://run-x.github.io/reference/google/modules/gcp-k8s-service/#container-resources) section.\nCPU is given in millicores, and Memory is in megabytes.\n",
"type": "object",
"properties": {
"cpu": {
diff --git a/modules/gcp_k8s_service/gcp-k8s-service.yaml b/modules/gcp_k8s_service/gcp-k8s-service.yaml
index b051b5f7b..8783f5ecb 100644
--- a/modules/gcp_k8s_service/gcp-k8s-service.yaml
+++ b/modules/gcp_k8s_service/gcp-k8s-service.yaml
@@ -66,12 +66,12 @@ inputs:
- name: autoscaling_target_cpu_percentage
user_facing: true
validator: any(str(), int(), required=False)
- description: See the [autoscaling](http://run-x.gihub.io/reference/google/modules/gcp-k8s-service/#autoscaling) section.
+ description: See the [autoscaling](http://run-x.github.io/reference/google/modules/gcp-k8s-service/#autoscaling) section.
default: 80
- name: autoscaling_target_mem_percentage
user_facing: true
validator: any(str(), int(), required=False)
- description: See the [autoscaling](http://run-x.gihub.io/reference/google/modules/gcp-k8s-service/#autoscaling) section.
+ description: See the [autoscaling](http://run-x.github.io/reference/google/modules/gcp-k8s-service/#autoscaling) section.
default: 80
- name: secrets
user_facing: true
@@ -91,12 +91,12 @@ inputs:
- name: healthcheck_path
user_facing: true
validator: str(required=False)
- description: See the See the [healthcheck probe](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `null` (i.e., no user-specified healthchecks)
+ description: See the See the [healthcheck probe](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `null` (i.e., no user-specified healthchecks)
default: null
- name: healthcheck_command
user_facing: true
validator: list(str(), required=False)
- description: See the See the [healthcheck probe](http://run-x.gihub.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `[]` (i.e., no user-specified healthchecks)
+ description: See the See the [healthcheck probe](http://run-x.github.io/reference/aws/modules/aws-k8s-service/#healthcheck-probe) section. Default `[]` (i.e., no user-specified healthchecks)
default: []
- name: liveness_probe_command
user_facing: true
@@ -138,7 +138,7 @@ inputs:
user_facing: true
validator: any(include('resources'), required=False)
description: |
- See the [container resources](http://run-x.gihub.io/reference/google/modules/gcp-k8s-service/#container-resources) section.
+ See the [container resources](http://run-x.github.io/reference/google/modules/gcp-k8s-service/#container-resources) section.
CPU is given in millicores, and Memory is in megabytes.
default:
cpu: 100
diff --git a/opta/cli.py b/opta/cli.py
index 91417997b..516292ee3 100755
--- a/opta/cli.py
+++ b/opta/cli.py
@@ -39,7 +39,7 @@ def cli() -> None:
Github: https://github.com/run-x/opta
- Documentation: http://run-x.gihub.io/
+ Documentation: http://run-x.github.io/
"""
pass
diff --git a/opta/commands/deploy.py b/opta/commands/deploy.py
index bbe28693f..973d21cf5 100644
--- a/opta/commands/deploy.py
+++ b/opta/commands/deploy.py
@@ -74,7 +74,7 @@ def deploy(
opta deploy -c my-service.yaml -i my-image:latest --local
- Documentation: http://run-x.gihub.io/features/custom_image/
+ Documentation: http://run-x.github.io/features/custom_image/
"""
@@ -92,7 +92,7 @@ def deploy(
fmt_msg(
"""
Opta deploy can only run on service yaml files. This is an environment yaml file.
- ~See http://run-x.gihub.io/getting-started/ for more details.
+ ~See http://run-x.github.io/getting-started/ for more details.
~
~(We think that this is an environment yaml file, because service yaml must
~specify the "environments" field).
diff --git a/opta/commands/secret.py b/opta/commands/secret.py
index 526ef0342..cc8416617 100644
--- a/opta/commands/secret.py
+++ b/opta/commands/secret.py
@@ -93,7 +93,7 @@ def secret() -> None:
opta secret view -c my-service.yaml "MY_SECRET_1"
- Documentation: http://run-x.gihub.io/features/secrets/
+ Documentation: http://run-x.github.io/features/secrets/
"""
pass
diff --git a/opta/commands/upgrade.py b/opta/commands/upgrade.py
index 2d8be69c5..c0eae5e45 100644
--- a/opta/commands/upgrade.py
+++ b/opta/commands/upgrade.py
@@ -48,7 +48,7 @@ def _upgrade() -> None:
except Exception:
logger.error(
"\nUnable to install latest version of Opta."
- "\nPlease follow the instructions on http://run-x.gihub.io/installation"
+ "\nPlease follow the instructions on http://run-x.github.io/installation"
)
finally:
_cleanup_installation_file()
diff --git a/opta/constants.py b/opta/constants.py
index 5c717d6ab..381348bf6 100644
--- a/opta/constants.py
+++ b/opta/constants.py
@@ -57,7 +57,7 @@
REDS: Final = (1, 9, 124, 160, 196)
-OPTA_INSTALL_URL: Final = "http://run-x.gihub.io/install.sh"
+OPTA_INSTALL_URL: Final = "http://run-x.github.io/install.sh"
successfull_upgrade: Final = os.path.join(
os.path.dirname(os.path.dirname(__file__)), ".successfull_upgrade"
)
diff --git a/opta/core/terraform.py b/opta/core/terraform.py
index 0017f22e9..c6d63e484 100644
--- a/opta/core/terraform.py
+++ b/opta/core/terraform.py
@@ -119,7 +119,7 @@ def insert_extra_env(cls, layer: "Layer") -> dict:
def validate_version(cls) -> None:
ensure_installed("terraform")
- pre_req_link = "Check http://run-x.gihub.io/installation/#prerequisites"
+ pre_req_link = "Check http://run-x.github.io/installation/#prerequisites"
current_version = Terraform.get_version()
current_parsed = version.parse(current_version)
diff --git a/opta/core/upgrade.py b/opta/core/upgrade.py
index d69ad622d..517dfc0aa 100644
--- a/opta/core/upgrade.py
+++ b/opta/core/upgrade.py
@@ -13,7 +13,7 @@
os.environ.get("OPTA_UPGRADE_CHECK_PROBABILITY", "0.2")
)
# TODO: Change this to the actual upgrade URL.
-UPGRADE_INSTRUCTIONS_URL = "http://run-x.gihub.io/installation/"
+UPGRADE_INSTRUCTIONS_URL = "http://run-x.github.io/installation/"
def _should_check_for_version_upgrade() -> bool:
diff --git a/opta/layer.py b/opta/layer.py
index de810db3a..69832704f 100644
--- a/opta/layer.py
+++ b/opta/layer.py
@@ -804,7 +804,7 @@ def _validate_providers(providers: dict) -> None:
if providers is None:
raise UserErrors(
"Environment Configuration needs a Provider Section.\n"
- "Please follow `http://run-x.gihub.io/getting-started/` to get started."
+ "Please follow `http://run-x.github.io/getting-started/` to get started."
)
"""
diff --git a/tests/core/test_terraform.py b/tests/core/test_terraform.py
index b63cafff0..a086cccec 100644
--- a/tests/core/test_terraform.py
+++ b/tests/core/test_terraform.py
@@ -59,7 +59,7 @@ def test_validate_version_low(self, mocker: MockFixture) -> None:
assert (
str(e.value)
- == "Invalid terraform version 0.14.9 -- must be at least 0.15.0. Check http://run-x.gihub.io/installation/#prerequisites"
+ == "Invalid terraform version 0.14.9 -- must be at least 0.15.0. Check http://run-x.github.io/installation/#prerequisites"
)
get_version.assert_called_once()
@@ -73,7 +73,7 @@ def test_validate_version_high(self, mocker: MockFixture) -> None:
assert (
str(e.value)
- == "Invalid terraform version 2.0.0 -- must be less than 2.0.0. Check http://run-x.gihub.io/installation/#prerequisites"
+ == "Invalid terraform version 2.0.0 -- must be less than 2.0.0. Check http://run-x.github.io/installation/#prerequisites"
)
get_version.assert_called_once()