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

Using Bicep module output as input for another module #181

Closed
lem-helbling opened this issue May 4, 2021 · 1 comment
Closed

Using Bicep module output as input for another module #181

lem-helbling opened this issue May 4, 2021 · 1 comment

Comments

@lem-helbling
Copy link

Describe the bug
When using a Bicep module output as an input for another Bicep module, whatif will not detect any changes. Neither additions nor modifications are shown in the list.

To Reproduce
Steps to reproduce the behavior:

  1. Run the deployment of the main.bicep file (see below) with whatif enabled
    az deployment group create --resource-group <resource-group> --template-file main.bicep -c
  2. The change list will not include the service bus as a new resource

File main.bicep:

module module1 'module1.bicep' = {
  name: 'Module 1'
}

module module2 'module2.bicep' = {
  name: 'Module 2'
  params: {
    input: module1.outputs.out
  }
}

File module1.bicep:

output out string = 'my-output'

File module2.bicep:

param input string

resource serviceBus 'Microsoft.ServiceBus/namespaces@2018-01-01-preview' = {
  name: 'Service Bus'
  location: 'westeurope'
}

Expected behavior
The service bus should be listed as a resource to create.

Client
CLI

@ghost ghost added the Needs Triage 🔍 label May 4, 2021
@alex-frankel
Copy link
Contributor

This is a dup of #157

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants