Skip to content

Commit b3e7c5c

Browse files
docs - fixing broken links (#305)
* Update 010 - evaluate-rest-apis.md * Update 010 - evaluate-rest-apis.md * Update 012 - quickstart-for-agent.md * Update 012 - quickstart-for-agent.md * hadolint version fixed Co-authored-by: Sohail Hussain <[email protected]>
1 parent ee4e644 commit b3e7c5c

File tree

5 files changed

+6
-6
lines changed

5 files changed

+6
-6
lines changed

.travis.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ jobs:
3434
dist: xenial
3535
script:
3636
- make -e lint
37-
- for f in `find scripts/dockerfiles -type f`; do echo $f; docker run --rm -i hadolint/hadolint < $f; done
37+
- for f in `find scripts/dockerfiles -type f`; do echo $f; docker run --rm -i hadolint/hadolint:v2.1.0 < $f; done
3838

3939
- stage: Tests
4040
name: coveralls

docs/readme-sync/v3.1/deploy-as-a-microservice/012 - quickstart-for-agent.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ updatedAt: "2020-08-17T20:51:52.458Z"
1111

1212
This brief quickstart describes how to run Agent, using two examples:
1313

14-
- To get started using Docker, see [Running locally via Docker](https://docs.developers.optimizely.com/full-stack/docs/quickstart-with-docker#section-running-locally-via-docker).
14+
- To get started using Docker, see the following section.
1515

1616
- To get started using example Node microservices, see the following video link.
1717

@@ -85,4 +85,4 @@ resp = s.post(url = 'http://localhost:8080/v1/activate', params=params, json=pay
8585
print(resp.json())
8686
```
8787

88-
The activate API is a POST to signal to the caller that there are side-effects. Namely, activation results in a "decision" event sent to Optimizely analytics for the purpose of analyzing Feature Test results. A "decision" will NOT be sent if the feature is simply part of a rollout.
88+
The activate API is a POST to signal to the caller that there are side-effects. Namely, activation results in a "decision" event sent to Optimizely analytics for the purpose of analyzing Feature Test results. A "decision" will NOT be sent if the feature is simply part of a rollout.

docs/readme-sync/v3.1/deploy-as-a-microservice/030 - use-optimizely-agent/010 - evaluate-rest-apis.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ metadata:
88
createdAt: "2020-02-21T17:44:53.019Z"
99
updatedAt: "2020-04-13T23:02:34.056Z"
1010
---
11-
Below is an example demonstrating the APIs capabilities. For brevity, we've chosen to illustrate the API usage with Python. Note that the API documentation is defined via an OpenAPI (Swagger) spec and can be viewed [here](https://library.optimizely.com/docs/api/agent/v1/index.htm).
11+
Below is an example demonstrating the APIs capabilities. For brevity, we've chosen to illustrate the API usage with Python. Note that the API documentation is defined via an OpenAPI (Swagger) spec and can be viewed [here](https://library.optimizely.com/docs/api/agent/v1/index.html).
1212

1313
## Start an http session
1414
Each request made into Optimizely Agent is in the context of an Optimizely SDK Key. SDK Keys map API requests to a specific Optimizely Project and Environment. We can setup a global request header by using the `requests.Session` object.

docs/readme-sync/v4.0/deploy-as-a-microservice/012 - quickstart-for-agent.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ updatedAt: "2021-03-15T23:02:34.056Z"
1111

1212
This brief quickstart describes how to run Agent, using two examples:
1313

14-
- To get started using Docker, see [Running locally via Docker](https://docs.developers.optimizely.com/full-stack/docs/quickstart-with-docker#section-running-locally-via-docker).
14+
- To get started using Docker, see the following section.
1515

1616
- To get started using example Node microservices, see the following video link.
1717

docs/readme-sync/v4.0/deploy-as-a-microservice/030 - use-optimizely-agent/010 - evaluate-rest-apis.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ metadata:
88
createdAt: "2020-02-21T17:44:53.019Z"
99
updatedAt: "2021-03-15T23:02:34.056Z"
1010
---
11-
Below is an example demonstrating the APIs capabilities. For brevity, we've chosen to illustrate the API usage with Python. Note that the API documentation is defined via an OpenAPI (Swagger) spec and can be viewed [here](https://library.optimizely.com/docs/api/agent/v1/index.htm).
11+
Below is an example demonstrating the APIs capabilities. For brevity, we've chosen to illustrate the API usage with Python. Note that the API documentation is defined via an OpenAPI (Swagger) spec and can be viewed [here](https://library.optimizely.com/docs/api/agent/v1/index.html).
1212

1313
## Start an http session
1414
Each request made into Optimizely Agent is in the context of an Optimizely SDK Key. SDK Keys map API requests to a specific Optimizely Project and Environment. We can setup a global request header by using the `requests.Session` object.

0 commit comments

Comments
 (0)