Skip to content

docs(containers): document VPC integration fields #2171

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jun 6, 2025
Merged

docs(containers): document VPC integration fields #2171

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 27 additions & 1 deletion packages_generated/container/src/v1beta1/types.gen.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -368,6 +368,9 @@ export interface Container {
* List of tags applied to the Serverless Container.
*/
tags: string[]
/**
* When connected to a Private Network, the container can access other Scaleway resources in this Private Network.
*/
privateNetworkId?: string
/**
* Command executed when the container starts. This overrides the default command defined in the container image. This is usually the main executable, or entry point script to run.
Expand Down Expand Up @@ -495,7 +498,8 @@ export interface Namespace {
*/
updatedAt?: Date
/**
* @deprecated
* @deprecated When activated, containers in the namespace can be connected to a Private Network.
Note that activating the VPC integration can only be done when creating a new namespace.
*/
vpcIntegrationActivated?: boolean
}
Expand Down Expand Up @@ -687,6 +691,11 @@ export type CreateContainerRequest = {
* Tags of the Serverless Container.
*/
tags?: string[]
/**
* When connected to a Private Network, the container can access other Scaleway resources in this Private Network.

Note: this feature is currently in beta and requires a namespace with VPC integration activated, using the `activate_vpc_integration` flag.
*/
privateNetworkId?: string
/**
* Command executed when the container starts. This overrides the default command defined in the container image. This is usually the main executable, or entry point script to run.
Expand Down Expand Up @@ -765,6 +774,9 @@ export type CreateNamespaceRequest = {
* Tags of the Serverless Container Namespace.
*/
tags?: string[]
/**
* When activated, containers in the namespace can be connected to a Private Network.
*/
activateVpcIntegration: boolean
}

Expand Down Expand Up @@ -1264,8 +1276,17 @@ export type UpdateContainerRequest = {
* @deprecated Number of maximum concurrent executions of the container.
*/
maxConcurrency?: number
/**
* Protocol the container uses.
*/
protocol?: ContainerProtocol
/**
* Port the container listens on.
*/
port?: number
/**
* Secret environment variables of the container.
*/
secretEnvironmentVariables?: Secret[]
/**
* Possible values:
Expand Down Expand Up @@ -1296,6 +1317,11 @@ export type UpdateContainerRequest = {
* Tags of the Serverless Container.
*/
tags?: string[]
/**
* When connected to a Private Network, the container can access other Scaleway resources in this Private Network.

Note: this feature is currently in beta and requires a namespace with VPC integration activated, using the `activate_vpc_integration` flag.
*/
privateNetworkId?: string
/**
* Command executed when the container starts. This overrides the default command defined in the container image. This is usually the main executable, or entry point script to run.
Expand Down
Loading