Skip to content

Commit

Permalink
chore: update hard-coded template string literal
Browse files Browse the repository at this point in the history
  • Loading branch information
vvagaytsev committed May 8, 2023
1 parent 26f22a6 commit ba9876a
Show file tree
Hide file tree
Showing 3 changed files with 7 additions and 7 deletions.
2 changes: 1 addition & 1 deletion core/src/plugins/kubernetes/sync.ts
Original file line number Diff line number Diff line change
Expand Up @@ -128,7 +128,7 @@ export interface KubernetesDeployDevModeSyncSpec extends DevModeSyncOptions {
containerName?: string
}

const exampleActionRef = templateStringLiteral("action.build.my-container-image.sourcePath")
const exampleActionRef = templateStringLiteral("actions.build.my-container-image.sourcePath")

export const kubernetesDeploySyncPathSchema = () =>
syncDefaultsSchema()
Expand Down
6 changes: 3 additions & 3 deletions docs/reference/action-types/Deploy/helm.md
Original file line number Diff line number Diff line change
Expand Up @@ -336,8 +336,8 @@ spec:
# defined.
#
# This should generally be a templated path to another action's source path (e.g.
# `${action.build.my-container-image.sourcePath}`), or a relative path. If a path is hard-coded, you must make
# sure the path exists, and that it is reliably the correct path for every user.
# `${actions.build.my-container-image.sourcePath}`), or a relative path. If a path is hard-coded, you must
# make sure the path exists, and that it is reliably the correct path for every user.
sourcePath: .

# POSIX-style absolute path to sync to inside the container. The root path (i.e. "/") is not allowed.
Expand Down Expand Up @@ -1126,7 +1126,7 @@ The name of a container in the target. Specify this if the target contains more

The local path to sync from, either absolute or relative to the source directory where the Deploy action is defined.

This should generally be a templated path to another action's source path (e.g. `${action.build.my-container-image.sourcePath}`), or a relative path. If a path is hard-coded, you must make sure the path exists, and that it is reliably the correct path for every user.
This should generally be a templated path to another action's source path (e.g. `${actions.build.my-container-image.sourcePath}`), or a relative path. If a path is hard-coded, you must make sure the path exists, and that it is reliably the correct path for every user.

| Type | Default | Required |
| ----------- | ------- | -------- |
Expand Down
6 changes: 3 additions & 3 deletions docs/reference/action-types/Deploy/kubernetes.md
Original file line number Diff line number Diff line change
Expand Up @@ -318,8 +318,8 @@ spec:
# defined.
#
# This should generally be a templated path to another action's source path (e.g.
# `${action.build.my-container-image.sourcePath}`), or a relative path. If a path is hard-coded, you must make
# sure the path exists, and that it is reliably the correct path for every user.
# `${actions.build.my-container-image.sourcePath}`), or a relative path. If a path is hard-coded, you must
# make sure the path exists, and that it is reliably the correct path for every user.
sourcePath: .

# POSIX-style absolute path to sync to inside the container. The root path (i.e. "/") is not allowed.
Expand Down Expand Up @@ -1070,7 +1070,7 @@ The name of a container in the target. Specify this if the target contains more

The local path to sync from, either absolute or relative to the source directory where the Deploy action is defined.

This should generally be a templated path to another action's source path (e.g. `${action.build.my-container-image.sourcePath}`), or a relative path. If a path is hard-coded, you must make sure the path exists, and that it is reliably the correct path for every user.
This should generally be a templated path to another action's source path (e.g. `${actions.build.my-container-image.sourcePath}`), or a relative path. If a path is hard-coded, you must make sure the path exists, and that it is reliably the correct path for every user.

| Type | Default | Required |
| ----------- | ------- | -------- |
Expand Down

0 comments on commit ba9876a

Please sign in to comment.