feat: add auto apply to env approvals

[sloloris]

Wait!

• Have you added comprehensive tests?
• Have you updated relevant data sources as well as resources?
• Have you updated the docs?

Testing

For any changes you make, please ensure your acceptance test conform to the following:

• every single new attribute is tested
• optional attributes revert to null or default values if removed
• attributes that interact interact as expected
• block values behave as expected when reordered
• nested fields on maps or list/set items function as expected. Terraform does not actually enforce most schema attributes on nested items
• each test step for a configuration is followed by a test step where ImportState and ImportStateVerify are set to true. ImportStateVerifyIgnore can be used if we explicitly expect a value to be different when imported, such as in the case of obfuscated values like API keys

LaunchDarkly Employees

For more information on how to build, test, and release, see the internal README on Confluence.

[ldhenry]

It looks like we're going to need to hook up ServiceNow in our acceptance test account. I can do this now.

[ldhenry]

It looks like we're going to need to hook up ServiceNow in our acceptance test account. I can do this now.

This is done now. I re-ran the tests but it's still failing because a template is not being specified. Also, you are likely to run into the error reported in #223 until the fix in REL-5726 is merged.

[sloloris]

It looks like we're going to need to hook up ServiceNow in our acceptance test account. I can do this now.

thank you!!! this is fixed, but we're now hitting the previously identified bug with the segment approvals config - i think possibly it may have been fixed for post creates but overlooked for patches. i am putting this back into draft mode while we address that first.

[blaqbern]

It looks like we're going to need to hook up ServiceNow in our acceptance test account. I can do this now.

thank you!!! this is fixed, but we're now hitting the previously identified bug with the segment approvals config - i think possibly it may have been fixed for post creates but overlooked for patches. i am putting this back into draft mode while we address that first.

Hmmm. The fix I did was for PATCH environment. Sounds like maybe it didn't work. I can dig into this

[ldhenry]

It looks like we're going to need to hook up ServiceNow in our acceptance test account. I can do this now.

thank you!!! this is fixed, but we're now hitting the previously identified bug with the segment approvals config - i think possibly it may have been fixed for post creates but overlooked for patches. i am putting this back into draft mode while we address that first.

Hmmm. The fix I did was for PATCH environment. Sounds like maybe it didn't work. I can dig into this

@blaqbern, I just re-ran the tests and the error is:

{"message":"The `serviceKind` and `serviceConfig` fields for `approvalSettings` and `resourceApprovalSettings` must match"}

This is slightly different than what it said previously:

{"message":"approvalSettings and resourceApprovalSettings service properties must match"}

I think that means we need to make a similar change for the serviceConfig