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 top level workspace optional in JSON schema #562

Merged
merged 2 commits into from
Jul 7, 2023
Merged

Conversation

shreyas-goenka
Copy link
Contributor

Tests

Tested manually. "workspace" is no longer a required field in the generated JSON schema

@shreyas-goenka shreyas-goenka changed the title Make workspace optional for bundle.yml Make top level workspace optional in JSON schema Jul 7, 2023
@shreyas-goenka shreyas-goenka enabled auto-merge (squash) July 7, 2023 13:04
@shreyas-goenka shreyas-goenka merged commit 47f4d30 into main Jul 7, 2023
4 checks passed
@pietern pietern deleted the workspace-opt branch July 7, 2023 13:10
@pietern pietern mentioned this pull request Jul 7, 2023
pietern added a commit that referenced this pull request Jul 10, 2023
## Changes

CLI:
* Fix secrets put-secret command
([#545](#545)).
* Fixed ignoring required positional parameters when --json flag is
provided ([#535](#535)).
* Update cp help message to not require file scheme
([#554](#554)).

Bundles:
* Fix: bundle destroy fails when bundle.tf.json file is deleted
([#519](#519)).
* Fixed error reporting when included invalid files in include section
([#543](#543)).
* Make top level workspace optional in JSON schema
([#562](#562)).
* Propagate TF_CLI_CONFIG_FILE env variable
([#555](#555)).
* Update Terraform provider schema structs
([#563](#563)).
* Update inline JSON schema documentation
([#557](#557)).

Dependencies:
* Bump Go SDK to v0.12.0
([#540](#540)).
* Bump github.com/hashicorp/terraform-json from 0.17.0 to 0.17.1
([#541](#541)).
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.

2 participants