-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add dependencies to manifest documentation. Add namespace to last versioned docs. #857
Open
seanson
wants to merge
1
commit into
okteto:main
Choose a base branch
from
seanson:420_add_dependencies_docs
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.
+78
−24
Open
Changes from all commits
Commits
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -96,6 +96,8 @@ Follow this document for a list of [environment variables](reference/okteto-cli. | |
|
||
Use `okteto deploy --dependencies` to force the redeployment of your dependencies. | ||
|
||
### dependencies - extended notation (object, optional) | ||
|
||
There is also an extended notation to configure how to deploy your dependency: | ||
|
||
```yaml | ||
|
@@ -111,22 +113,45 @@ dependencies: | |
timeout: 15m | ||
``` | ||
|
||
Or: | ||
#### repository (string) | ||
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. I would use the same format that we use in the build section. We put the sample first, and then a list of items explaining each field |
||
|
||
A reference to a git repository that holds the manifest for your dependency. | ||
|
||
#### manifest (string, optional) | ||
|
||
A path in the dependency repository that points to an Okteto YAML. When specifying the manifest path, the dependency deployment will use this path where the manifest is defined as the context. | ||
|
||
#### branch (string, optional) | ||
|
||
The branch to use for your dependency git repository. | ||
|
||
#### variables (map[string]string, optional) | ||
|
||
Variables to pass to the dependency in string map format. | ||
|
||
```yaml | ||
dependencies: | ||
frontend: | ||
repository: https://github.com/okteto/movies-frontend | ||
manifest: okteto.yaml | ||
branch: main | ||
variables: | ||
- ENVIRONMENT: development | ||
- DEBUG: true | ||
wait: true | ||
timeout: 15m | ||
variables: | ||
ENVIRONMENT: development | ||
DEBUG: true | ||
``` | ||
|
||
#### variables ([string], optional) | ||
|
||
Variables to pass to the dependency in a list of strings format. | ||
|
||
```yaml | ||
variables: | ||
- ENVIRONMENT: development | ||
- DEBUG: true | ||
``` | ||
|
||
When specifying the manifest path, the dependency deployment will use this path where the manifest is defined as the context. | ||
#### wait (boolean, optional) | ||
|
||
Wait for all resources in the dependency to become healthy before continuing. | ||
|
||
#### timeout (string, optional) | ||
|
||
Maximum time to be waiting for creating the dependency until an error is returned. | ||
|
||
### deploy ([string], optional) | ||
|
||
|
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
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.
Let's remove this line. That way everything is index under
dependencies
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.
Is there a good way we can communicate that this property has a simple and an extended notation then? I like the idea of the formatting being consistent but need a way as a consumer to know that there are two explicit versions. (Sidenote, is there a YAML schema for the Okteto file somewhere?)
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.
We don't have a YAML schema for the Okteto Manifest yet 😥
Are you familiar with any documentation where they document different field types?
I have been looking for inspiration, but didn't find anything great