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

Document purpose of terraform-yaml resource in terraform jobs #911

Merged
merged 3 commits into from
Oct 15, 2024

Conversation

jameshochadel
Copy link
Contributor

@jameshochadel jameshochadel commented Oct 10, 2024

Changes proposed in this pull request:

  • I think this input is unused. If an operator knows why it's there, let me know and I'll keep it, and add a comment explaining its purpose. In the deploy-cf jobs, it's used by the terraform-secrets steps, but I cannot find any step that takes it as an input in the terraform jobs.
  • The input is used to trigger the jobs, but not used as an input to the jobs. This PR documents the setup.

security considerations

None. Removing unused code.

@jameshochadel jameshochadel requested a review from a team as a code owner October 10, 2024 21:20
rcgottlieb
rcgottlieb previously approved these changes Oct 10, 2024
bengerman13
bengerman13 previously approved these changes Oct 10, 2024
@dandersonsw
Copy link
Contributor

It looks like it's there to trigger the terraform plan jobs if there's been a change in the tf state file for each deployment

@jameshochadel
Copy link
Contributor Author

@dandersonsw Aha. Let me make sure I understand. These resources watch the state bucket for changes. When there's an update, it triggers the job. The resource itself is not an input to any step, just a trigger. The job then gets the state through an independent method — the standard data "terraform_remote_state" ... approach.

Sound right? If yes, I'll add a little comment, since this managed to trick several of us. Thanks!

@dandersonsw
Copy link
Contributor

@jameshochadel That is correct, as far as I can tell the only purpose of that resource is to act as a trigger when there's been a change

@jameshochadel jameshochadel changed the title Remove unused terraform-yaml input from terraform jobs Document purpose of terraform-yaml resource in terraform jobs Oct 15, 2024
@jameshochadel jameshochadel merged commit 2f51cbe into main Oct 15, 2024
2 checks passed
@jameshochadel jameshochadel deleted the drop-unused-input branch October 15, 2024 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants