Closed samuel-phan closed 5 months ago
This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days
@antonbabenko Would you have some time to take a look at this PR please? 🙇
This PR is included in version 6.7.0 :tada:
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Description
Add a variable
trigger_on_package_timestamp
(boolean - defaults totrue
) to whether use timestamp to trigger the package creation or not.Motivation and Context
Problem
terraform apply
. The lambda is created.builds
directory (to simulate a CICD job with an empty environment).terraform plan
again, it will detect a drift because the timestamp has changed.One solution was to add the variable
recreate_missing_package = false
, but when the CICD job (without anybuilds
directory) runsterraform apply
will face this error:Solution
Add a variable
trigger_on_package_timestamp
(boolean - defaults totrue
) to whether use timestamp to trigger the package creation or not.Fix #396
Breaking Changes
None.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull requestI have added an
example/simple-cicd
with atest.sh
inside to run the test scenario.