feat: remove archive_file resource deprecated status
#367
Conversation
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
|
|
codymaust
changed the title
archive_file deprecated statusarchive_file resource deprecated status
|
i was also unsure how to classify this semantically, but settled on |
codymaust
force-pushed
the
feat/reinstate-archive-file-resource
branch
from
d62db5d to
6a40586
Compare
|
the branch has been updated |
1 task
- from what i gathered from the git history, this resource was introduced in `v2.3.0` in a deprecated state - discussion with the community involving @bendbennett resulted in the consideration of this deprecation being removed (see: hashicorp#218) - since `v2.x` there has been a strong focus on keeping this provider limited to the `data` source, so some of this proposed change is taking a best guess at what makes sense while trying not to depart from the overall approach - i acknowledge that this appears to be in some ways orthogonal to the goal of the project, but there has been little movement in regards to this widely-requested feature (understandably so, based on reasons mentioned above). - there are cases, primarily in a remote build server context, where the design decisions/limitations of the `data` source makes the adoption and usage of this provider much more challenging. this change is proposed as a stop-gap until a larger focus is able to put on this project by the primary contributing team
codymaust
force-pushed
the
feat/reinstate-archive-file-resource
branch
from
6a40586 to
d2c1b70
Compare
SBGoods
reviewed
Nov 19, 2024
Co-authored-by: Selena Goods <[email protected]>
SBGoods
approved these changes
Nov 19, 2024
There was a problem hiding this comment.
Thank you for the contribution, @codymaust! I really appreciate the thoroughness with the documentation changes.
|
Hello All, Quick check: Does the version 2.7.0 released? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
thank you all for an immensely useful provider
from what i gathered from the git history, this resource was
introduced in
v2.3.0in a deprecated statediscussion with the community involving @bendbennett resulted in the
consideration of this deprecation being removed (see: archive_file data source gets created during "terraform plan" vs "terraform apply" and also is not deleted during destroy #218)
since
v2.xthere has been a strong focus on keeping this providerlimited to the
datasource, so some of this proposed change is takinga best guess at what makes sense while trying not to depart from the
overall approach
i acknowledge that this appears to be in some ways orthogonal to the
goal of the project, but there has been little movement in regards to
this widely-requested feature (understandably so, based on reasons
mentioned above).
there are cases, primarily in a remote build server context, where the
design decisions/limitations of the
datasource makes the adoption andusage of this provider much more challenging.
this change is proposed as a stop-gap until a larger focus is able to
put on this project by the primary contributing team
fixes #218