Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
O
OpenTofu
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
components
OpenTofu
Commits
fe10af05
Commit
fe10af05
authored
1 week ago
by
Alex Maras
Browse files
Options
Downloads
Patches
Plain Diff
fix: use extra_artifacts input argument
parent
dd6defda
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
tests/integration-tests/ExtraArtifactsAreIncluded.gitlab-ci.yml
+1
-1
1 addition, 1 deletion
...integration-tests/ExtraArtifactsAreIncluded.gitlab-ci.yml
with
1 addition
and
1 deletion
tests/integration-tests/ExtraArtifactsAreIncluded.gitlab-ci.yml
+
1
−
1
View file @
fe10af05
...
@@ -11,7 +11,7 @@ include:
...
@@ -11,7 +11,7 @@ include:
root_dir
:
$TEST_GITLAB_TOFU_ROOT_DIR
root_dir
:
$TEST_GITLAB_TOFU_ROOT_DIR
state_name
:
$TEST_GITLAB_TOFU_STATE_NAME
state_name
:
$TEST_GITLAB_TOFU_STATE_NAME
warning_on_non_empty_plan
:
true
warning_on_non_empty_plan
:
true
plan
_artifacts
:
extra
_artifacts
:
-
$ARTIFACT_FILE_NAME
-
$ARTIFACT_FILE_NAME
# For CI Terraform state cleanup
# For CI Terraform state cleanup
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment