template/template_stack: can't both be enforced yet conflicting

[cyphermox]

Likely closes #294

The template and template_stack objects are enforced when running plan/apply against imported objects; otherwise the engine would want to completely replace the objects, which would likely cause consistency issues with the rest of the configuration.

Since they are both enforced; they can't also be conflicting; that leads to an impossible scenario where you must but can't define both a template and template_stack.

Signed-off-by: Mathieu Trudel-Lapierre mtrudel@stack8.com

Description

Make these schema fields not conflicting

Motivation and Context

See above

How Has This Been Tested?

I am running this against a subset of my production config with good results (ie. terraform plan shows no changes to be applied when running the proposed code, with template_stack and template both set on panorama-defined zones).

Types of changes

• Bug fix (non-breaking change which fixes an issue)

Checklist

• [x] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes if appropriate.
• [x] All new and existing tests passed.

[welcome-to-palo-alto-networks[bot]]

:tada: Thanks for opening this pull request! We really appreciate contributors like you! :raised_hands:

[cyphermox]

This isn't tested yet, I need to figure out how to build the provider first. I submitted the PR right away to have a discussion if the approach is right; I believe making changes non-destructive is more important than preserving this particular conflict in the schema.

[cyphermox]

Yeah, that code change alone doesn't seem to work; I've built the provider and using it locally, but it still complains about conflicts.

[cyphermox]

@shinmog I think this is ready for review.