-
Notifications
You must be signed in to change notification settings - Fork 229
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
docs(srv): add troubleshooting on testing private resources MTA-5424 #4211
Open
SamyOubouaziz
wants to merge
4
commits into
main
Choose a base branch
from
MTA-5424
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
--- | ||
meta: | ||
title: How to test a container | ||
description: Instructions for testing your Serverless Containers on Scaleway. | ||
content: | ||
h1: How to test a container | ||
paragraph: Instructions for testing your Serverless Containers on Scaleway. | ||
tags: container serverless test-container | ||
dates: | ||
validation: 2025-01-14 | ||
posted: 2025-01-15 | ||
categories: | ||
- serverless | ||
--- | ||
|
||
This page shows you how to execute Serverless Containers from the [Scaleway console](https://console.scaleway.com). The **Test** feature of a container allows you to run your code using a selection of methods to make sure it behaves as expected. | ||
|
||
<Macro id="requirements" /> | ||
|
||
- A Scaleway account logged into the [console](https://console.scaleway.com) | ||
- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization | ||
- [Created a container](/serverless/containers/how-to/deploy-container/) | ||
|
||
1. Click **Containers** in the **Serverless** section of the side menu. The containers page displays. | ||
|
||
2. Click the relevant containers namespace. A list of your containers displays. | ||
|
||
3. Click the name of the container you want to test. | ||
|
||
4. Open the **Test** tab. | ||
|
||
5. Select the **method** you want to use from the drop-down menu. | ||
|
||
6. Enter the **path** to your container. Leave the default `/` value if the host of your container is not located in a specific folder. | ||
|
||
7. Click **+ Advanced options** to add any required HTTP header or parameter to your container. | ||
|
||
8. Click **Run**. | ||
|
||
The **Output** section displays the response from your container and the status code. | ||
|
||
<Message type="note"> | ||
If you encounter a message error while testing your container, refer to the [dedicated troubleshooting](/serverless/containers/troubleshooting/tests-fail-on-private-container/) for more information. | ||
</Message> |
26 changes: 26 additions & 0 deletions
26
serverless/containers/troubleshooting/tests-fail-on private-container.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
--- | ||
meta: | ||
title: Tests fail on private Serverless Containers | ||
description: I get error messages when testing private Serverless Containers using the Scaleway Console | ||
content: | ||
h1: Tests fail on private Serverless Containers | ||
paragraph: I get error messages when testing private Serverless Containers using the Scaleway Console | ||
tags: serverless containers private troubleshooting issue error test authentication token unable | ||
dates: | ||
validation: 2025-01-14 | ||
posted: 2025-01-14 | ||
categories: | ||
- serverless | ||
--- | ||
|
||
## Problem | ||
|
||
I get error messages when testing private Serverless Containers using the Scaleway Console. | ||
|
||
### Cause | ||
|
||
[Private](/serverless/containers/concepts/#privacy-policy) containers require a `X-Auth-Token` HTTP header when being run or tested. | ||
|
||
### Possible solutions | ||
|
||
Make sure that you have [created an authentication token](/serverless/containers/how-to/create-auth-token-from-console/) from the Scaleway console, and passed it as a HTTP header while [testing your container](/serverless/containers/how-to/test-a-container). | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
26 changes: 26 additions & 0 deletions
26
serverless/functions/troubleshooting/tests-fail-on-private-function.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,26 @@ | ||||||
--- | ||||||
meta: | ||||||
title: Tests fail on private Serverless Functions | ||||||
description: I get error messages when testing private Serverless Functions using the Scaleway Console | ||||||
content: | ||||||
h1: Tests fail on private Serverless Functions | ||||||
paragraph: I get error messages when testing private Serverless Functions using the Scaleway Console | ||||||
tags: serverless functions private troubleshooting issue error test authentication token unable | ||||||
dates: | ||||||
validation: 2025-01-14 | ||||||
posted: 2025-01-14 | ||||||
categories: | ||||||
- serverless | ||||||
--- | ||||||
|
||||||
## Problem | ||||||
|
||||||
I get error messages when testing private Serverless Functions using the Scaleway Console. | ||||||
|
||||||
### Cause | ||||||
|
||||||
[Private](/serverless/functions/concepts/#privacy-policy) functions require a `X-Auth-Token` HTTP header when being run or tested. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
### Possible solutions | ||||||
|
||||||
Make sure that you have [created an authentication token](/serverless/functions/how-to/create-auth-token-from-console/) from the Scaleway console, and passed it as a HTTP header while [testing your function](/serverless/functions/how-to/test-a-function). | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.