Skip to content

Commit

Permalink
Updated the description message (#983)
Browse files Browse the repository at this point in the history
* Updated the description message

* Updated the description message
  • Loading branch information
av3esha committed May 17, 2024
1 parent 3b9de19 commit 6d99d26
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions docs/resources/platform_pipeline.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ resource "harness_platform_pipeline" "example" {
store_type = "REMOTE"
repo_name = "repoName"
}
tag = {}
tags = {}
yaml = <<-EOT
pipeline:
name: name
Expand Down Expand Up @@ -157,7 +157,7 @@ resource "harness_platform_pipeline" "test" {
- `git_import_info` (Block List, Max: 1) Contains Git Information for importing entities from Git (see [below for nested schema](#nestedblock--git_import_info))
- `import_from_git` (Boolean) Flag to set if importing from Git
- `pipeline_import_request` (Block List, Max: 1) Contains parameters for importing a pipeline (see [below for nested schema](#nestedblock--pipeline_import_request))
- `tags` (Set of String) Tags to associate with the resource.These should match the tag value passed in the yaml; If this parameter is null or not passed, the tags specified in yaml should also be null.
- `tags` (Set of String) Tags to associate with the resource. These should match the tag value passed in the YAML; if this parameter is null or not passed, the tags specified in YAML should also be null.
- `template_applied` (Boolean) If true, returns Pipeline YAML with Templates applied on it.
- `template_applied_pipeline_yaml` (String) Pipeline YAML after resolving Templates (returned as a String).
- `yaml` (String) YAML of the pipeline. In YAML, to reference an entity at the organization scope, prefix 'org' to the expression: org.{identifier}. To reference an entity at the account scope, prefix 'account` to the expression: account.{identifier}. For eg, to reference a connector with identifier 'connectorId' at the organization scope in a stage mention it as connectorRef: org.connectorId.
Expand Down
2 changes: 1 addition & 1 deletion examples/resources/harness_platform_pipeline/resource.tf
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ resource "harness_platform_pipeline" "example" {
store_type = "REMOTE"
repo_name = "repoName"
}
tag = {}
tags = {}
yaml = <<-EOT
pipeline:
name: name
Expand Down
2 changes: 1 addition & 1 deletion internal/service/platform/pipeline/resource_pipeline.go
Original file line number Diff line number Diff line change
Expand Up @@ -166,7 +166,7 @@ func ResourcePipeline() *schema.Resource {
}

helpers.SetProjectLevelResourceSchema(resource.Schema)
resource.Schema["tags"].Description = resource.Schema["tags"].Description + "These should match the tag value passed in the yaml; If this parameter is null or not passed, the tags specified in yaml should also be null."
resource.Schema["tags"].Description = resource.Schema["tags"].Description + " These should match the tag value passed in the YAML; if this parameter is null or not passed, the tags specified in YAML should also be null."
return resource
}

Expand Down

0 comments on commit 6d99d26

Please sign in to comment.