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

Make step outputs available #42

Open
almisson opened this issue Oct 26, 2021 · 1 comment
Open

Make step outputs available #42

almisson opened this issue Oct 26, 2021 · 1 comment

Comments

@almisson
Copy link

Currently, step outputs aren't accessible from outside of runiac/terraform. It would be nice if runiac could provide a mechanism so that after running steps the outputs from those steps were available in some way. Specific use case example:

We have runiac/terraform configured to provision a resource group and an app service in that resource group. The resources follow a specific naming convention, something like "app-dev-adam-abc123" for the app service. After creating the resources with runiac, we want to deploy a package to the web app, using azure CLI, i.e. az webapp deployment. The inputs to that command take a resource group name and a web app name. Rather than define the naming convention in two places, it'd be nice if we could just use the output from one of the runiac steps which would contain the web app name. (Additionally, we are actually suffixing resources names with a unique value generated in terraform, so we can't define the convention outside of relying on the output from runiac/terraform.)

@erikpaasonen
Copy link
Contributor

FYI this appears to be the same engineering problem as retrieving outputs from another Terraform stack. Hashicorp has a list of suggestions on how to solve this. If you're Azure only I'm sure the Amazon S3 entry can be easily adapted to use the azurerm_storage_blob resource and data source. HTH.

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

No branches or pull requests

2 participants