Skip to content
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

New terraform_data managed resource to replace null_resource #31757

Merged
merged 3 commits into from Dec 12, 2022

Conversation

jbardin
Copy link
Member

@jbardin jbardin commented Sep 8, 2022

Add a new managed resource, terraform_data, which incorporates and enhances the functionality of null_resource, making use of features not available through the legacy SDK.

This new resource has 4 attributes:

  • id: A unique computed string.
  • triggers_replace: A value of any type which will trigger replacement when changed.
  • input: A value of any type, which will be reflected in output after apply.
  • output: Computed from the input value, which during plan will be unknown of the same type as input, and identical to input after apply.

This gives us a built-in replacement for null_resource, while adding some key new features; the ability to store and reference data of any arbitrary type, and create unknown values during plan via the input and output attributes.

Documentation updates will be handled in a separate PR.

@jbardin jbardin changed the title terraform_data New terraform_data managed resource to replace null_resource Nov 29, 2022
@jbardin jbardin requested a review from a team December 5, 2022 14:13
@jbardin jbardin marked this pull request as ready for review December 5, 2022 14:13
Replace and enhance the `null_resource` functionality with a new
`terraform_data` managed resource.
Rename `triggers` to be more descriptive, making it similar to
`replace_triggered_by`.
@github-actions
Copy link

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.

@github-actions
Copy link

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 contributions.
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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants