New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjust Application Connectivity docs to Kyma 2.0, pt.2 #12465
Conversation
✔️ 🥰 Documentation preview ready! 🥰 🔨 Explore the source changes: 0e4601f 🔍 Inspect the deploy log: https://app.netlify.com/sites/kyma-project-docs-preview/deploys/61968f994305210007447212 😎 Browse the preview: https://deploy-preview-12465--kyma-project-docs-preview.netlify.app |
…o AC modes to AC overview intro
…from the Application CR doc
docs/01-overview/main-areas/application-connectivity/ac-05-useful-links.md
Outdated
Show resolved
Hide resolved
docs/01-overview/main-areas/application-connectivity/ac-05-useful-links.md
Outdated
Show resolved
Hide resolved
docs/01-overview/main-areas/application-connectivity/ac-05-useful-links.md
Outdated
Show resolved
Hide resolved
@@ -83,18 +84,28 @@ A successful call returns the following response: | |||
} | |||
``` | |||
|
|||
> **NOTE:** The response contains URLs to the Application Registry API and the Events Publisher API, however, it is not recommended to use them. You should call the `metadata` endpoint URL, which is provided in `api.infoUrl` property, to fetch correct URLs to the Application Registry API and to the Events Publisher API, and other configuration details. | |||
> **NOTE:** The response contains URLs to the Application Registry API and the Events Publisher API, however, using them is not recommended. You should call the `metadata` endpoint URL, which is provided in the **api.infoUrl** property, to fetch correct URLs to the Application Registry API and to the Events Publisher API, and other configuration details. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The second sentence feels a bit too long. Can we chunk it into two shorter ones?
docs/03-tutorials/00-application-connectivity/ac-05-call-registered-service-from-kyma.md
Outdated
Show resolved
Hide resolved
docs/04-operation-guides/operations/ra-01-enable-kyma-with-runtime-agent.md
Show resolved
Hide resolved
docs/04-operation-guides/operations/ra-01-enable-kyma-with-runtime-agent.md
Show resolved
Hide resolved
docs/04-operation-guides/operations/ra-01-enable-kyma-with-runtime-agent.md
Outdated
Show resolved
Hide resolved
docs/04-operation-guides/operations/ra-01-enable-kyma-with-runtime-agent.md
Outdated
Show resolved
Hide resolved
docs/03-tutorials/00-application-connectivity/ac-05-call-registered-service-from-kyma.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
docs/03-tutorials/00-application-connectivity/ac-09-get-api-specification.md
Outdated
Show resolved
Hide resolved
…pitalization for systems
…d remove '-k' from curl commands
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
… export as env var, fix typo in KEY file name
## Call Application Registry and Event Publisher on local deployment | ||
|
||
Since the local Kyma installation uses the self-signed certificate by default, skip TLS verification. | ||
|
||
Call Application Registry with this command: | ||
|
||
```bash | ||
curl https://gateway.local.kyma.dev/{APP_NAME}/v1/metadata/services --cert {CLIENT_CERT_FILE_NAME}.crt --key {KEY_FILE_NAME}.key -k | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed this part, 'cause we don't want to have commands for local deployment specifically, just mention to skip cert verification (we have such a note at the top of the document), and if we turn it into a general command working for both a local and remote cluster, it becomes the same as the command in the previous section.
openssl req -new -sha256 -out generated.csr -key generated.key -subj "/OU=OrgUnit/O=Organization/L=Waldorf/ST=Waldorf/C=DE/CN={APP_NAME}" | ||
openssl base64 -in generated.csr | ||
openssl req -new -sha256 -out $CSR_FILE_NAME.csr -key $KEY_FILE_NAME.key -subj "/OU=OrgUnit/O=Organization/L=Waldorf/ST=Waldorf/C=DE/CN=$APP_NAME" | ||
openssl base64 -in $CSR_FILE_NAME.csr -A |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added -A
here because it gets rid of the newlines in the printed CSR, which I otherwise have to remove manually.
2. Export the ID of the registered service and the Namespace in which to create the Function that calls the service as environment variables: | ||
|
||
```bash | ||
export SERVICE_ID={YOUR_SERVICE_ID} | ||
export NAMESPACE={YOUR_NAMESPACE} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added exporting the Namespace to an env var back here since I mistakenly removed it before.
Description
Update the Application Connectivity 2.0 docs to Kyma 2.0
Changes proposed in this pull request:
APP_NAME
,CLUSTER_DOMAIN
,CLIENT_CERTIFICATE_FILE_NAME
,KEY_FILE_NAME
,SERVICE_ID
.Related issue(s)
#11047