Is your feature request related to a problem? Please describe.
Currently, in the configuration blocks of env0_environment, you can define is_required = true. This is mostly pretty meaningless, as the purpose of is_required is to make sure that a value is supplied in deploy time (which is basically the configuration block in this case)
So, removing the configuration block that has is_required = true is not going to work, and fail with failed deploying environment: 400 Bad Request: Missing required environment variable(s).
A workaround is to remove the is_required and apply, and only later remove the configuration block
Describe the solution you'd like
is_required should be removed from the configuration block of environments. We need to first deprecate the field, and remove it later down the road in a minor/major version change
Describe alternatives you've considered
An alternative is an env0-wide change, to change the behaviour of required variables and make them removable. This approach has its own downfalls, though
Is your feature request related to a problem? Please describe.
Currently, in the
configurationblocks ofenv0_environment, you can defineis_required = true. This is mostly pretty meaningless, as the purpose ofis_requiredis to make sure that a value is supplied in deploy time (which is basically theconfigurationblock in this case)So, removing the
configurationblock that hasis_required = trueis not going to work, and fail withfailed deploying environment: 400 Bad Request: Missing required environment variable(s).A workaround is to remove the
is_requiredand apply, and only later remove theconfigurationblockDescribe the solution you'd like
is_requiredshould be removed from theconfigurationblock of environments. We need to first deprecate the field, and remove it later down the road in a minor/major version changeDescribe alternatives you've considered
An alternative is an env0-wide change, to change the behaviour of required variables and make them removable. This approach has its own downfalls, though