This code can generate a new PAC Version eq. like an update. In the UI it is mentioned as "Create new Branch".

Description

I added a new method to the "pac_files" class which can generate a new PAC Version. This will make it possible to do the Change via CLI instead of going to the UI and edit the PAC in the UI and create a new Branch etc.

Additionally it gives the customer the possibilities to push the change to different PAC Files without editing each one in the UI.
If he has test policies like initial, extended and productive he could do a change in the PAC Content and push it via CLI to the UI and test it.

Also it would be possible to push the change directly to initial and extended tests for a bigger testing group.

closes #238

Has your change been tested?

I tested the code already in the Zscalerbeta cloud and pushed some changes to the Cloud:

I was adding a comment via CLI:
// This is a Test via Zscaler SDK number | Now with verify PAC
and requested the User input for Commit:
commit_message = input("Enter the commit message: ")

In the UI I'm able to see the Commit Message and the Comment:

But you can test the method by your own too.

I tested the code with our Zscalerbeta cloud and configured a PAC File locally with some changes in the Code and pushed it with this steps:
Reading the File as paccontent
request user Input for Commit
request user Input for PAC file to deploy the paccontent
validate PAC via method
activate change

After this I took the PAC URL and downloaded the file once and checked the file I created and the downloaded one.

There is no impact to the current deployed code since this is a new method in the pac_file class.

Types of changes

Modify

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [X ] My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• This change is using publicly documented and stable APIs.