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

Decompiler is not aware, that @description is allowed on outputs #4896

Closed
rahalan opened this issue Oct 18, 2021 · 0 comments · Fixed by #5887
Closed

Decompiler is not aware, that @description is allowed on outputs #4896

rahalan opened this issue Oct 18, 2021 · 0 comments · Fixed by #5887
Labels
enhancement New feature or request story: decompiler

Comments

@rahalan
Copy link

rahalan commented Oct 18, 2021

Bicep version
Bicep CLI version 0.4.613 (d826ce8)

Describe the bug
Since PR 4091 #4091 the Outputs support the @description('my description') decorator. If you build a bicep file with that, it creates the "metadata": {"description": "value"} in the json file. But if you go the other way round and decompile the json file, which has the metadata declared for an output, it does not create the @description in the bicep file.

To Reproduce
1.) create json with an output, like:

"outputs": {
        "virtualMachinesResourceGroup": {
            "type": "string",
            "value": "[resourceGroup().name]",
            "metadata": {
                "description": "The name of the Resource Group the VM(s) was/were created in."
            }
        }
    }

2.) run bicep decompile xxx.json

3.) look at the created bicep file in the output section, there is the output but no description on it

@alex-frankel alex-frankel added this to the Committed Backlog milestone Oct 18, 2021
@ghost ghost locked as resolved and limited conversation to collaborators May 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request story: decompiler
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants