-
Notifications
You must be signed in to change notification settings - Fork 178
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
chore: Allows to to run acceptance tests for a published Atlas provider version #1789
Merged
Merged
Changes from 7 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
b567958
allow to pass ref to acc tests
lantoli c302520
run acc tests for latest published version
lantoli 71c705e
add ref in workflow call
lantoli 0a88e3b
TEMPORARY - run always acc-tests-latest-published
lantoli 09aaad4
Revert "TEMPORARY - run always acc-tests-latest-published"
lantoli 42687d9
TEMPORARY - don't check if trigger is schedule
lantoli 5e4623f
Revert "TEMPORARY - don't check if trigger is schedule"
lantoli 01871e7
undo changes in Test Suite
lantoli 4cdb2af
clarify provider version param
lantoli db66691
clarify TF version and that can use x for patch
lantoli 5d07af4
clarify provider_matrix
lantoli 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
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 |
---|---|---|
|
@@ -34,8 +34,16 @@ jobs: | |
secrets: inherit | ||
uses: ./.github/workflows/cleanup-test-env.yml | ||
|
||
acc-tests-latest-published: | ||
needs: clean-before | ||
if: ${{ github.event_name == 'schedule' && !cancelled() }} | ||
secrets: inherit | ||
uses: ./.github/workflows/acceptance-tests.yml | ||
with: | ||
ref: 'v1.14.0' | ||
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. pending to calculate instead of hardcoding |
||
|
||
mig-tests: | ||
needs: [clean-before, versions] | ||
needs: [acc-tests-latest-published, versions] | ||
if: ${{ !cancelled() }} | ||
strategy: | ||
max-parallel: 1 | ||
|
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.
I am struggling to see the value of adding this job to run daily, given that the results will be the same unless there is a new patch release from TF.
If you can provide more context in the PR or reference where this requirement was discussed that would be great. I am thinking why we cannot rely on our master branch to see if the latest patch version of TF is breaking some functionality in our provider.
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.
the use case here is that Hashicorp releases a new version, e.g. 1.6.7 and breaks our latest published version, e.g. 1.14.0. it's true that results won't change while Hashicorp doesn't publish a new version. But the alternative is that we have to be pending (or automate?) when a new version is published and then run on demand.
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.
@Zuhairahmed what do you think?
alternatively we can do that, don't run every night but on demand when we know that a new Hashicorp version came out.
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.
@AgustinBettati at the moment I'll leave only the option to run it manually